Markup language system, method, and computer program product

ABSTRACT

A system, method, and computer program product are provided for use in connection with at least one computer-readable Extensible Markup Language (XML)-compliant data document capable of including: a plurality offline items with a plurality of data values, and a plurality of computer-readable semantic tags that describe a semantic meaning of the data values.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/724,794, filed May 28, 2015, which, in turn, is acontinuation-in-part (for the purposes of providing a glossary inaccordance with the Glossary Pilot Program) of application Ser. No.12/222,751, filed Aug. 15, 2008 which, in turn, is a divisional ofapplication Ser. No. 09/573,778, filed May 18, 2000, now U.S. Pat. No.7,421,648, which, in turn, claims priority to Provisional U.S. PatentApplication No. 60/135,525, filed on May 21, 1999, and Provisional U.S.Patent Application No. 60/183,152, filed on Feb. 17, 2000, which are allincorporated herein by reference.

The following identified U.S. patent applications are also relied uponand are incorporated by reference in this application.

U.S. patent application Ser. No. 09/573,780 (now U.S. Pat. No.7,650,355) entitled “Reusable Macro Markup Language,” filed on May 18,2000.

U.S. patent application Ser. No. 09/573,419 (now U.S. Pat. No.7,249,328), entitled “Tree View for Reusable Data Markup Language,”filed on May 18, 2000.

U.S. patent application Ser. No. 09/573,413 (now U.S. Pat. No.6,920,608), entitled “Chart View for Reusable Data Markup Language,”filed on May 18, 2000.

FIELD OF THE INVENTION

The present invention relates generally to data processing systems and,more particularly, to a computer markup language for use in a databrowser and manipulator.

SUMMARY

A system, method, and computer program product are provided for use inconnection with at least one computer-readable Extensible MarkupLanguage (XML)-compliant data document capable of including: a pluralityof line items with a plurality of data values, and a plurality ofcomputer-readable semantic tags that describe a semantic meaning of thedata values.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a high level diagram of a Reusable Data Markup Language(RDML) data viewer, its inputs and outputs in accordance with methodsand systems consistent with the present invention;

FIG. 2 depicts a data processing system suitable for use with methodsand systems consistent with the present invention;

FIG. 3 depicts a diagram of the interrelation of various RDML softwareand hardware components shown in FIG. 2;

FIG. 4 depicts the use of an RDML formatter shown on FIGS. 2 and 3 toadd markup tags to data;

FIG. 5 depicts a screen shot of a database/document tab and managementscreen of the RDML formatter depicted in FIGS. 2 and 3;

FIG. 6 depicts a flowchart of the steps performed when accessing theRDML document server depicted in FIGS. 2 and 3;

FIG. 7A depicts internal architecture of the RDML data viewer depictedin FIGS. 2 and 3;

FIG. 7B depicts a legend of the meaning of the symbols depicted in FIG.7A;

FIG. 8 depicts a flowchart of the steps performed by the RDML dataviewer in a method for downloading, processing and displaying an RDMLdocument in accordance with methods and systems consistent with thepresent invention;

FIG. 9 illustrates elements of an RDML Document Type Definition inaccordance with methods and systems consistent with the presentinvention;

FIG. 10 depicts a flowchart of steps used to automatically manipulate anRDML document for display using line item attributes in accordance withmethods and systems consistent with the present invention;

FIG. 11 depicts a flowchart of the steps performed by the x-valuetransformer depicted in FIG. 7A to store a new document in the primarydata store;

FIGS. 12A-12C depicts X-Y plots and tree views in accordance withmethods and systems consistent with the present invention;

FIG. 13 depicts a primary data store of the RDML data viewer as shown inFIG. 7A;

FIGS. 14A-14F depict a chart view and tree view of the RDML data vieweras depicted in FIG. 7A in accordance with methods and systems consistentwith the present invention;

FIGS. 15A-15C depict flowcharts of the steps performed by a graphicaluser interface, chart manager and chart data object for adding a lineitem to a chart view upon selection of the line item in a tree view inaccordance with methods and systems consistent with the presentinvention;

FIG. 16 depicts a spreadsheet view and a chart view of the data viewerin accordance with methods and systems consistent with the presentinvention; and

FIG. 17 depicts a footnote view of the data viewer and a chart view inaccordance with methods and systems consistent with the presentinvention;

FIG. 18 illustrates elements of a Reusable Macro Markup Language (RMML)Document Type Definition in accordance with the present invention;

FIGS. 19A-19C depict RMML document handling, an RMML graphicalinterface, and an RMML macro interpreter, respectively, in accordancewith the present invention;

FIGS. 20A-20D illustrates screen shots of RMML macro panels inaccordance with the present invention.

FIG. 21 shows a flowchart illustrating steps used in a method fortagging information from spreadsheets in accordance with the presentinvention; and

FIGS. 22A-22D depicts exemplary screen shots of the tagging ofspreadsheet information tagging to create a document in accordance withthe present invention.

DETAILED DESCRIPTION Glossary

HTML=HyperText Markup Language

Measurement=characteristics necessary to describe the measurementaspects of the domain the number is taken from

Structure=structuring of the data in within a table

Tagging=adding metadata

RDML=Reusable Data Markup Language

XML=Extensible Markup Language

Methods and systems in accordance with the present invention provide amarkup language, referred to as Reusable Data Markup Language (“RDML”),that permits the browsing and manipulation of numbers and provide arelated data viewer that acts as a combination Web browser andspreadsheet/analytic application that may automatically read numbersfrom multiple online sources and manipulate them without humanintervention. Using the markup language, users may browse online sourcesusing numerical-based queries, and the data viewer may automaticallycombine and manipulate multiple documents on a single display.

In accordance with an implementation consistent with the presentinvention, a method in a data processing system is provided thatreceives a first markup document and a second markup document, both thefirst markup document and the second markup document containingnumerical values and tags reflecting characteristics of the numericalvalues. The method automatically combines the first markup document andthe second markup document into a single data set and displays thesingle data set.

In accordance with another implementation, a method in a data processingsystem is provided that receives a document containing numerical values,and receives indications of characteristics of the numerical values, thecharacteristics including a unit and a magnitude. Further, it adds thereceived indications into the document as tags associated with thenumerical values to create a markup document.

In accordance with yet another implementation, a method in a dataprocessing system is provided that receives a markup document having aset of numerical values and tags indicating characteristics of thenumerical values and determines a transformation for the set ofnumerical values to reflect new characteristics. The method thenaccesses a plurality of the tags of the set of numerical values, theplurality of the tags indicating magnitude, scale, modifier, units,measure, adjustment and aggregation. Furthermore, the method determinesconversion factors for the magnitude, scale, modifier, units, measure,adjustment and aggregation tags to accomplish the transformation to thenew characteristics and multiplies the set of numerical values by thedetermined conversion factors to transform the set of numerical valuesto reflect the new characteristics.

Methods and systems in accordance with the present invention provide achart view that automatically manipulates and graphically displaysnumerical data. The manipulation and display is based on attributesassociated with the numerical data describing characteristics of thenumerical data. The chart view facilitates the simultaneous display ofdifferent series of numerical values of different types on a singlechart and automatically displays appropriate descriptive textualcomponents (e.g., axis labels, axis titles, chart titles, numberprecision, legends, footnotes, axis scales, etc.) The chart view allowssingle click transformations of series of numerical values and providesautomatic formatting of descriptive textual components in response.

In accordance with an implementation of the present invention, a methodin a data processing system having a display showing a chart is providedthat receives a series of numerical values with tags indicatingcharacteristics of the numerical values and displays the numericalvalues on the chart. Further, the method automatically determines atitle for the numerical values based at least one of the tags anddisplays the determined title on the chart.

In accordance with another implementation of the present invention, amethod in a data processing system having a display showing a chart isprovided that receives a first series of numerical values having tagsindicating characteristics of the numerical values and displays thefirst series of numerical values on the chart, the first series ofnumerical values corresponding to a first axis on the chart. The methodfurther receives a second series to be added to the chart, the secondseries of numerical values having tags indicating characteristics of thesecond series of numerical values and automatically generates a secondaxis on the chart. Finally, the method displays the second series ofnumerical values on the chart corresponding to the second axis while thefirst series is displayed on the chart.

In accordance with yet another implementation of the present invention,a method in a data processing system having a display showing a chart isprovided that receives an instruction to display a series of numericalvalues on the chart on the display, the numerical values having tagsindicating characteristics of the numerical values, and displays theseries of numerical values on the chart in response to the receivedinstruction. The method then automatically formats the chart based on atleast one of the tags in response to the received instruction.

In accordance with another implementation of the present invention, adata processing system is provided comprising a memory storing acharting application configured to manipulate and display numericaldata, the memory having a selected series of numerical values having atag indicating text information associated with the numerical values.The data processing system further comprises a display showing a charthaving a legend that displays the text information associated with theselected series of numerical values. The legend word-wraps and scrollsthe text information associated with the series of numerical data whenthe text information does not fit on the legend on the chart. The systemfurther comprises a processor for running the charting application.

Methods and systems in accordance with the present invention provide atree view that automatically manipulates and graphically displaysnumerical data. The tree view facilitates the simultaneous display ofdifferent series of numerical values of different types on a singledisplay and automatically displays descriptive textual components. Thetree view allows single click transformations of series of numericalvalues and provides automatic formatting of descriptive textualcomponents in response. It further visually displays the relationshipbetween series of numerical data for a user while supplying the userwith hyperlinks associated with a given series of numerical data.

In accordance with an implementation of the present invention, a methodin a data processing system is provided that receives a first and asecond series of numerical values, and determines the relationshipbetween the first and second series of numerical values. The method thendisplays an icon depicting the relationship between the first and secondseries of numerical values based on the determined relationship.

In accordance with another implementation of the present invention, amethod in a data processing system is provided that receives a series ofnumerical values and a link associated with the series of numericalvalues, the link having a list of associated hyperlinks. The methoddisplays the series of numerical values and the associated link, andreceives an instruction to activate the link. Further, the methoddisplays the list of hyperlinks associated with the link in response tothe received instruction.

In accordance with yet another implementation of the present invention,a method in a data processing system having a display showing a chart isprovided that receives a series of numerical values having associatedmetadata documentation. The method further receives an instruction toselect the series of numbers and displays the series of numerical valueson the chart while displaying the metadata documentation associated withthe series of numerical values.

In accordance with another implementation of the present invention, adata processing system is provided that comprises a memory having aprogram for manipulating numerical values, and storing a first series ofnumerical values and a second series of numerical values. The dataprocessing system further comprises a display that displays the firstand second series of numerical values and a relationship icon depictingthe relationship between the first series of numerical values and thesecond series of numerical values. Finally, the data processing systemfurther comprises a processor for running the program.

Methods and systems in accordance with the present invention provide amarkup language, referred to as Reusable Macro Markup Language (“RMML”),for producing and utilizing macros which are reusable numerical analysisroutines which can be written quickly, cheaply, and in a form usable bya broad range of data documents in RDML, the platform upon which themacros are run.

RMML allows reusable spreadsheet type macros to be posted as webdocuments, to be, searched by search engines, to be combined into morecomplex programs, and to be reused with many data documents. RMML bringsto spreadsheet manipulation routines the economic and productivitybenefits of (1) standardization, (2) interchangeable parts, (3)specialization and assembly-line techniques in creation, and (4)economies of scale in creation and deployment. In addition, RMML bringsto spreadsheet macros and numerical programming, some of the benefits ofthe World Wide Web: (1) widespread accessibility on demand, (2) abilityto search for documents (in this case, search for capabilities andbehavior of routines instead of text or data), and (3) the ability tohyperlink documents (including the ability of macros to call each otherremotely).

In accordance with an implementation of the present invention, a dataprocessing system method is provided that receives a macro defined toperform an operation on a series of numerical values and receives aseries of numerical values having tags indicating characteristics of thenumerical values. The method then performs an operation defined by themacro on the series of numerical values using the indicatedcharacteristics.

In accordance with another implementation of the present invention, adata processing system method is provided that receives a macro definingan operation on a set of numerical values and receives a vector ormatrix of numerical values. The method then performs an operationdefined by the macro using the vector or matrix as a variable in theoperation.

In accordance with yet another implementation of the present invention,a data processing system is provided that includes a memory containing anumerical analysis program having a macro defined to perform anoperation on a series of numerical values, and a series of numericalvalues having tags indicating characteristics of the numerical values.It further comprises a processor for running the program such that theprogram performs an operation defined by the macro on the series ofnumerical values using the indicated characteristics, and a display fordisplaying results of the operation.

Because of the length of the detailed description, the following tableof contents is provided.

Topic Section Reusable Data Markup Language Overview I Reusable MacroMarkup Language Overview I.A System Hardware Components II SystemOverview III System Details IV Internal Data Viewer Architecture IV.ADocument Type Definition IV.A.1 Reader, Parser and Processor IV.A.2X-value Transformer and Line Item Set Types IV.A.3 Primary Data StoreIV.A.4 Chart View IV.A.5 Tree View IV.A.6 Spreadsheet View IV.A.7Footnote View IV.A.8 Tagging Wizard IV.A.9 Aspects of RDML DocumentsIV.A.1O Graphical User Interface and HTML browser IV.B Reusable MacroMarkup Language IV.C RMML Macro Package IV.C1

I. RDML Overview

Methods and systems consistent with the present invention provide amarkup language, referred to as Reusable Data Markup Language (“RDML”),and a data viewer referred to as the RDML data viewer that is used toretrieve, manipulate and view documents in the RDML format. Generally,RDML permits the browsing and manipulation of numbers, and allows theviewer to act as a combination Web browser and spreadsheet/analyticapplication that may automatically read numbers from multiple onlinesources, understand their meaning, and manipulate them without humanintervention. The RDML data viewer may use the Internet to obtainrequested sets of numbers like HTML does for text. Using RDML, it ispossible to form a search on the Internet that is a true query ofnumbers. One such request is the creation of a list of quarterlyrevenues from 1996 to 1997 pertaining to companies with sales growthgreater than 10 percent and no taxable income. After receiving anyrequested sets of numerical data, the data viewer may automaticallytransform and combine them even if they are in different formats (i.e.,one in thousands of U.S. dollars and another in hundreds of Frenchfrancs) on a single graphical display without requiring the user to makemanual adjustments. The user may then make single-click adjustments tothe display (e.g., adjust for inflation, currencies, time periods,number precision, etc.) to see different aspects of the receivedinformation. RDML generally facilitates numerical browsing byassociating numbers with attributes describing the meaning of thenumbers.

Although the preferred embodiment of RDML is a markup language that is afully compliant implementation of XML version 1.0, other implementationsare possible. XML is described in detail in “XML Bible,” Elliotte RustyHarold, IDG Books Worldwide, 1999, which is incorporated herein byreference. The RDML data viewer is a data browser, data manipulator,data viewer (in the form of charts, spreadsheets, etc.) and general userinterface for data documents. It greatly extends the capabilitiesprovided by current spreadsheet and database management programs. Inaddition to extended capabilities, it lowers costs to businesses bypermitting efficient reuse of data, functions, and report formats.

The RDML data viewer works with RDML formatted data documents, which arefiles that may be stored locally, over a network, including theInternet, or in any combination of sources. The structure of the RDMLdata files allows the RDML data viewer to act as a combination browserand analytic program, such as a spreadsheet, which can automaticallyread, interpret and manipulate numbers in its integrated analyticprogram. The RDML data viewer also provides a “macro” development andmanagement scheme which allows users to create custom routines for themanipulation, transformation and display of RDML-formatted data. Macrosand related aspects are described in greater detail below.

FIG. 1 depicts a high-level diagram of an RDML data viewer 100, itsinputs and its outputs in accordance with methods and systems consistentwith the present invention. Generally, data viewer 100 may be softwarethat resides in the memory of a computer and accepts several types ofinput 102, 104 and 106, one of which is the RDML data document 102. TheRDML data document 102 may be an ASCH text document formatted with RDMLtags which are compliant with XML version 1.0. In one implementationconsistent with the present invention, the tags of an RDML data document102 are advantageously structured to include documentation of the dataand arrange data in “line items,” a collection of data values that issimilar to a “record” or “row” in a relational database (discussedbelow). In RDML, the line item is generally the basic unit ofcalculation, as opposed to a single data value or cell as is typicalwith most conventional databases or spreadsheets. RDML documents 102contain sets of line items, such sets being analogous to “tables” inrelational databases, and documentation (“metadata”) regarding the “lineitem sets.” The RDML data document 102 is read by the RDML data viewer100 which stores the data internally, making it available to a number of“views” 108, which present the data in different ways (charts, tables,etc.) to a user (not shown). The views 108 are also referred to asprograms or applications, as they can be standalone software programsthat receive their data from the RDML data viewer 100.

Analysis routines can be developed for data and placed in their owndocuments referred to as Reusable Macro Markup Language (“RMML”) MacroDocuments 104 which are another input to the data viewer 100 and areoptional. These routines are reusable; they can be applied to virtuallyany data document meeting the requirements set forth in the RMMLdocument 104. For example, an RMML document 104 may contain routines forconverting RDML data to different currencies, and any data denominatedin currency can use the RMML currency conversion macro. The preferredembodiment of RMML is also a fully compliant implementation of XMLversion 1.0, although other embodiments are possible.

Similarly, Reusable Data Style Language (“RDSL”) style sheets 106,another optional input to the data viewer 100, can be applied to datadocuments to create specially-formatted output reports: A RDSL is afully compliant implementation of Extensible Style Language (“XSL”)which is described in detail in “XML Bible,” Elliotte Rusty Harold, IDGBooks Worldwide, 1999. These RDSL documents 106 are XSL-compliant stylesheets which essentially act as report writers for RDML data documents102. A typical use would be for data documents containing corporatefinancial statements. A single RDML data document 102 may contain a setof financial statements, but several different style sheets could beapplied: one to show the data in annual columns, one to show it in aquarterly breakdown, one to show it in European format, and so forth.The RDML data viewer 100 automatically combines data documents 102 andstyle documents 106 to create reports.

RDML dramatically reduces the expense, time, and complexity of datamanipulation by addressing the aforementioned problems of documentationof data, non-standardization of analytic routines, and lowconceptual-level calculations of data. RDML addresses the problem of theseparation of data and its documentation by encapsulating data and itsdocumentation together in machine-readable form that can be usedinteractively. This differs from the approach of conventional relationaldatabases in which data is kept in the computer and the documentationtypically kept in a three-ring binder or other printed document. Theseparation of data and its documentation often ensures the need forhigh-priced database programmers every time the data must be accessed,used or transferred. Documentation in RDML also differs from that ofspreadsheets, which tend to be personal in that the documentation is inthe head and personal notes of the creator. In one implementationconsistent with the present invention, RDML encapsulatesmachine-readable documentation with the data. The data and itsdocumentation (metadata) are used together by the data viewer 100 tointerpret what the numbers mean, how they are to be used, and how theyare to be displayed. The small up-front investment in refining the rawdata pays off in the lessened need for human labor to access and reusethe data in the future. RDML incorporates several important types ofmetadata: sources, contacts, license requirements, expirations andupdate information, data types, data classes, handling instructions(e.g., what to do with nulls, missing values, etc.), units andmeasurements, and other information needed to produce the variouspresentations.

Use of RDML addresses the problem of non-standardization by definingstandards for both data characteristics and analytic routine interfaces.Standardization leads to component reuse, automation of production, andmore rapid development of product enhancements. While the computerindustry has developed standards for file formats and function-levelinterfaces, it has not developed general data format or content-analysisstandards. For example, once data is input to an application (whetherspreadsheet, database or other), the user may want to manipulate thedata and see basic statistics for the different line items (sums,averages, % changes, variances, and so forth), adjustments for standardchanges (adjustments for inflation, conformance to industry indexes, %of stock market averages, etc.), or standard ratios (debt/equity,price/earnings, etc.). Because there is neither a standard general dataformat, nor a standard analytic routine interface, users currentlycreate each of these manipulation routines from primitive coding. Inspreadsheets, they must input formulas and conversion factors number bynumber, and in databases, they must write SQL queries or otherprogramming routines to manipulate the data.

RDML provides both the data standard and the function interface formanipulation routines. This means that a routine can be written to applyto any line item that meets the conditions it imposes, and theseroutines are reusable. Currently, conventional spreadsheet macros (oneanalogue to RDML macros 104) are typically only used in the spreadsheetfor which they were designed. The macros cannot typically be used inanother spreadsheet where the numbers may be in different cells or indifferent units. RDML macros 104 are not dependent on cell position, orhuman intervention to conform data: they can be directly used by othersfor other data sets. If a user writes a routine which, for instance,calculates and graphs a moving average of a time series, it can be usedby any time series in any RDML document 102.

While solving documentation and standardization problems, use of RDMLalso addresses the problem of calculations occurring at too low aconceptual level by creating data “objects” at the line item anddocument levels, whereas conventional spreadsheets operate only at thecell (single number) level. For instance, calculations that may becommon to a set of data, i.e., a line item, may operate more efficientlybecause they can be applied once, as opposed to being appliedindividually to many different single numbers or cells. Furthermore,analytic routines (macros) can be combined, applied successively, orused by inheritance to create new routines. The line item orientationdramatically reduces the number of formulas that need to be written (oneper line instead of one per number). It also increases the readabilityof program code, because the user can review the logic at a higher levelof abstraction.

In addition to solving these problems, RDML reduces costs, time, andcomplexity for operations on the side of the data consumer, the datapublisher and the program developer. To utilize and manipulate data,typically, a user retrieving data over the Internet views a text versionof the data, prints the data (in HTML, ASCII or PDF format), and thentypes the numbers into a spreadsheet or database program. The RDML dataviewer 100 automates this process by making the data immediatelyavailable to other programs as interpretable data: the user does notneed to retype it. Upon locating numerical sets of data from multipleonline sources, the data viewer 100 automatically normalizes, collates,transforms, and formats the data.

Some conventional systems make data available for download as data ineither a common spreadsheet format (such as Lotus or Excel), or in acomma-delimited or other common text format. This at least saves theuser the necessity of retyping certain numbers, but creates a newproblem of manipulating the data to get it into a more usable form(e.g., normalized, standardized).

As such, RDML (and its related data viewer) “normalizes” data for addedefficiency. Normalizing data is primarily a matter of conforming keyfields, including matching dissimilar fields, resolving conflicts incategories, resolving the handling of duplicates, etc. In order to beuseful, data should be conformed to a format that can be read by anapplication (such as a graphing routine, or calculation routine). Forexample, the application may expect data aggregated by year, whereas theincoming data may be aggregated by month. The user must manipulate theinput to make it conform to the form expected by the application. RDMLperforms these tasks automatically, using embedded documentationregarding the input data to make any necessary conforming changes to theinput. In the time series example above, RDML, would aggregate themonthly data into yearly data, using embedded documentation to determinewhether the aggregation should be a sum, an average, etc.

Additionally, comparing data is a primary use of spreadsheets. Examplesinclude comparing the financial statements of different companies,comparing the statistics from different states, and comparing differenteconomic lime series. When these data categories come from differentsources, they are usually not directly compatible: the user must lay outthe data items on a spreadsheet or similar program in a manner similarto assembling a jigsaw puzzle. As with normalization, RDML usesdocumentation embedded in the various input files to determine howdifferent line items and values should be collated.

Once data is normalized and collated, the RDML data viewer 100transforms the data automatically. Conventionally, users typically makea series of adjustments to the numbers in the data set. The input datamay be, for example, denominated in “millions of dollars,” while outputis desired in “billions of yen.” RDML provides a set of indicators forthe most common transformations, permitting automatic machinetranslation of the numbers from their input state to the state desiredby the user.

A conventional method of formatting data for output on a PC is tocut-and-paste the data to a formatting application (word processor,graph generator, spreadsheet or other), and then mark up the data tochange the format to the desired output. This is time consuming and notrepeatable—if the data is input again with a slight change, the wholeformatting process must be repeated. The RDML data viewer 100 avoids thecut-and-paste approach by saving the original data in a central storageobject (described below) in the data viewer 100 and applying separateformatting instructions to create different views 108. The user canswitch among views 108 with a single mouse click and the program handlesall format and numerical conversions for the user.

In some of the more advanced database management systems, a“report-writer” approach is used. Like the RDML data viewer 100, thisapproach applies a template to a centrally stored dataset. The problemis that the data sets are not standardized; a report writer templatewritten for one dataset cannot typically be used for another. RDML,however, provides for reuse of style sheets in the same manner itprovides reuse of data and macros.

In addition to the above-mentioned problems, RDML solves problemsrelating to “live” connections of numerical data involving multiplesources that typically require programming expertise. Whether the aim isto draw numbers from multiple sources over a wide area network (e.g.,the Internet) or over a corporate LAN, incorporating remote data iscomplicated by many issues: connection protocols, programming languagedependencies, data type inconsistencies, error handling, datatransformations, etc. Programmers can surmount these problems at acertain expense, but not in a flexible way that permits reuse, and usersagain rely on custom programming. In response to the cost, timerequirements, and inflexibility of the custom programming approaches,casual users resort to labor-based solutions. In a typical case, afinancial spreadsheet is created with, for example, ten assumptionsrelated to interest rates. Every time the spreadsheet is used, thecreator looks the numbers up in the newspaper and types the results intothe appropriate cells, and any necessary transformations are made byhand. RDML removes the need for custom programming and manual input byproviding a way to include numbers from remote RDML documents 102 innormal formulas. The RDML data viewer 100 automatically looks to thespecified address on the web to retrieve the numbers, makes anynecessary transformations (for example, from yen to current dollars) andplaces the result in the correct formula. In this way, an RDML document102 or macro 104 can draw on multiple documents at once. Because itsdocumentation is machine-readable, it can be read by multiple systems,none of which need be aware of the physical layout or data types of theothers.

Lastly, the use of RDML enables client-side processing usingInternet-supplied data thereby realizing a number of advantages. Afterdata is retrieved, analytic routines (macros) are performed on theclient side, as opposed to the conventional approach in web-based dataanalysis, in which the analytic routines are performed on the serverside. Whereas sensitive data and calculations can remain local in theRDML data viewer 100, the user need not fear that sensitive data isbeing misused by a company running a server, or that data is beingmisappropriated over the web. Additionally, it increases speed becauseupdates to graphs, reports and spreadsheets can be near instantaneousbecause there is no need for the round-trip Internet transmission, orthe loading and execution of a routine on a busy server. Users may alsoprefer local copies of data that they control and to which they—haveimmediate access.

I.A. RMML Overview

Methods and systems in accordance with the present invention providemacros and RMML, which allow numerical analysis routines to be writtenquickly, cheaply, and in a form that is usable by a broad range of datadocuments in RDML. RMML macros provide reusable user-definedcalculations for use in conjunction with RDML that automaticallymanipulate and display numerical data contained in RDML markupdocuments. RMML also allows spreadsheet type macros to be posted as webdocuments, to be searched by search engines, to be combined into morecomplex programs, and to be reused with many data documents.

For example, a user viewing a chart having a series of data in an RDMLdata viewer may apply, with one mouse click, a macro to that chart andsee an instantaneous (or nearly instantaneous) transformation of thecharted series of data. Not only is the data changed, but the titles,legends, footnotes, axis scales and other properties are also changed.As a further example, a user may be looking at a time series trend ofautomobile sales in millions of dollars. By clicking on a macro entitled“% change”, the chart recalculates itself according the percentagechange from period to period. The y-axis title changes from “$ millions”to “% annual change”, etc. Table manipulation macros may perform suchfunctions as combining two tables into one, sorting a table, searchingfor certain line items and other database-like tasks. Othertransformation macros may perform other functions such as wordtranslation, data format translation, and report-writing.

RMML macros are highly reusable because they are made available in across-platform, text-based, searchable, XML-compliant format. Becausethe macros are portable, they have much greater marketability. RMML alsobuilds into its language tags for many types of documentation so that amacro may be reused and understood by the original macro writer as wellas other users.

Conventional spreadsheet programs typically base references on physicallocations, a problem RMML avoids by referring to numbers by theirposition in a chart or formula, or by tag names, thus allowing thenumbers themselves to be anywhere in a document. RMML macros also usethe measurement and the meaning of numbers because RDML tags containstandard vocabularies to identify the measure, magnitude, scale, unit,precision, class, etc. of the numbers, and the RMML interpreter handlesdifferences for the user.

Additionally, RMML builds error handling into its interpreter and makesavailable automated testing tools to help increase the quality of thecode. Users may also graphically change parameters for the macros usingcheck boxes, slider bars, input boxes, and selection lists, and RMMLmakes it easy for the author of a macro to add those visual components.

Below is a detailed description of RDML, the platform upon which RMMLmacros run, followed by a detailed description of RMML.

II. System Hardware Components

FIG. 2 depicts a data processing system 200 that is suitable for usewith methods and systems consistent with the present invention. Dataprocessing system 200 comprises a computer 201 and a server computer 203interconnected via a network 214, such as the Internet, where the servercomputer 203 may provide RDML documents 102 to computer 201. Computer201 includes a central processing unit (CPU) 202, a main memory 204, asecondary storage device 206, a display 210 and an input device 212.

The main memory 204 may include the RDML data viewer 100 which may be apersonal computer-based program, although one skilled in the art willappreciated that the data viewer may reside elsewhere. In addition tothe data viewer 100 which includes views 108 for display, the mainmemory 204 includes related software components that may be used toinput RDML documents 102, macro documents 104, and style sheets 106 tothe data viewer. It may include the RDML document formatter 216 which auser uses to apply tags to numerical data, and/or an RDMLdocument server218 which provides RDML documents 102 to the data viewer 100. The mainmemory 204 may also comprise an RDML document editor 220 used to editthe files of RDML documents 102 and RDSL style sheet editor 222 forcreating style sheets 106. The RDML/XML search engine 224, whichsearches RDML documents in response to queries, may also reside inmemory 204 along with any additional plug-in applications 225. Each ofthese components and their interactions are described below in greaterdetail.

The memory 204 may include various software components of the dataviewer 100 and related components which may be programmed inobject-oriented languages such as the Java™ programming language. TheJava™ programming language is described in further detail in “The JavaProgramming Language,” 2nd Ed., Ken Arnold, James Gosling,Addison-Wesley, 1998, which is incorporated herein by reference. Forfurther description of the Java Language, reference should be made to“The Java Language Specification,” James Gosling, Bill Joy, Guy Steele,Addison-Wesley, 1996 which is also incorporated herein by reference.However, one skilled in the art will appreciate that other programminglanguages may be used. The RDML data viewer 100 may download RDML datadocuments 102 from many different sources such as a local storage diskor from a server over network 214.

The secondary storage 206 may include the RDML image database 226 whichstores documentation tag data regarding RDML document 102, and the RMMLmacro software development kit 228 for developing macros. The secondarystorage may also store existing databases 230 for holding original datafrom which RDML documents 102 are created. These components may also bestored in main memory or on another remote computer and are alsodescribed in greater detail below.

FIG. 2 also depicts a web server 232 on computer 203 that interacts withthe computer 201 via network 214. In one system consistent with thepresent invention, the web server 232 sends RDML documents 102 over thenetwork 214 and may be connected to a disk array 234 which holds RDMLdata documents 102. This disk array 234 may receive data documents 102from the database server 236 which may receive data from databasestorage 238. Protocols used in the transmission of information betweenthe server 232 and the computer 201 include, but are not limited to,HTTP and FTP.

One skilled in the rut will appreciate that aspects of methods andsystems consistent with the present invention may be stored on or readfrom other computer readable media besides memory like secondarydevices, such as hard disks, floppy disks, and CD ROM, or a carrier wavefrom a network (such as the Internet). Additionally, one skilled in theart will also appreciate that the data processing system may containadditional or different components.

III. System Overview

FIG. 3 illustrates an RDML system consistent with the present inventionand the relationships between the various components. These variouscomponents may reside in a memory 204 on a computer such as computer201. Existing databases 230 store data that can be used to create RDMLdocuments 102, and generally the data is extracted into either a “flatfile” format (e.g., coma-delimited, or fixed-width fields) or a formreadable by Java Database Connectivity (“JDBC”). RDML documents 102 maybe structured to model flat files so that a single RDML document 102encapsulates a set of rows and columns. Examples of databases includeSQL server by Microsoft and Oracle 8 server.

The RDML document formatter 216 is a graphical tool used by the user toreduce the amount of manual labor required to combine data and itsdocumentation. The contents of an existing database 230 may not beenough to create an RDML document 102, because in one system consistentwith the present invention, RDML uses documentation of the contents.Such documentation often may be found in a printed volume and hence mustbe manually input and manually combined with the data. The RDMLformatter 216 allows a user (or data publisher) to map data fields froma relational database, flat file, spreadsheet file or text document toRDML data documents 102. It also allows a data publisher to adddocumentation to the data file (RDML data document 102) itself.

The RDML image database 226 is a relatively small database maintained bythe RDML formatter 216 to hold information necessary to recreate an RDMLdocument 102 should the underlying data change. It eliminates the needfor the user to manually input the documentation again because the RDMLimage database 226 stores it.

An RDML document server 218 functions when RDML documents 102 are beingcreated dynamically. The server 218 queries the existing database 230for the desired line items, queries the image database 226 fordocumentation items and instructions for constructing the RDML document102, and finally creates a valid, well-formed RDML document.

The RDML document editor 220 allows users to edit RDML documents 102which typically are ASCII text files (which may contain UNICODE data).As such, they may be edited by any text-oriented editor or wordprocessor. This is, however, a time-consuming and error-prone approachto marking up an RDML (or any XML) file. A specialized RDML documenteditor 220 allows a user to quickly make changes, check for errors, andview information on the data and metadata. The document editor 220 mayoperate over the Internet: users possessing the correct permissions tomodify a file can make updates or changes to the underlying RDML datadocument 102 by issuing commands from the RDML data viewer 100.

An RDML document 102 may be an ASCII/UNICODE text file used to transmitdata and metadata to the RDML Data Viewer 100. It can be stored locally,or can be transmitted over network 214 such as a corporate LAN or theInternet (using HTTP, FTP, email, etc.). To be a valid RDML document102, the file conforms to the RDML Document Type Definition (“DTD”)which is described in detail below. The DTD describes required andoptional data elements, their ordering, syntax, and the controlledvocabulary for use in certain data elements. DTDs in general are alsodescribed in “XML: Extensible Markup Language,” Elliotte Rusty Harold,IDG Books Worldwide, 1998.

The RDML data viewer 100 functions as a combination RDML and HTMLbrowser, object-oriented spreadsheet, report-writer, and applicationplatform. The browser functions read HTML or RDML documents 102; HTMLdocuments are rendered immediately in a browser window, while RDMLdocuments are first cached in an internal data object (conforming to theDOM—“Document Object Model”—standard discussed below) and then renderedin views 108 selected by the user. The default view is typically a chartand a tree listing, although several other default views are available.The RDML data viewer 100 uses the cached RDML data objects to createviews 108, employing a variety of transformation and manipulationobjects to get the data to match either the form expected by the view,or to match the fom1 of other data objects with which it is beingcombined.

The RDML Macro Software Development Kit (“SDK”) 228 allows a functiondesigner to create functions that can be applied generally to any datadocument that contains the types of data necessary for the function. TheSDK is a collection of macro-writing tools, including an IDE(“Integrated Development Environment”), an editor, an object browser,and a validation tester.

RDML generally separates the form of data from general calculationroutines that operate on that data. By separating format from functions,both the data and the functions can be made reusable. In conventionalspreadsheets, for example, numbers can be placed in arbitrary cellsselected by the creator. If a second developer decides to create ananalytic function, that developer must know what row and column eachnumber is in. That routine will then not work with another spreadsheetunless the exact same row and column structure is followed.

Applying functions generally creates one form of software reuse: usersneed not tell the function where their data is (the approach of“wizards” in traditional spreadsheets). A second form of reuse is thatgained by inheritance: function developers can choose the existingfunction that most closely matches what they are trying to do, andsimply make the necessary edits to create the desired new function. TheSDK 228 permits a third type of reuse in the ability to attach to remotedata documents and remote macros on the web to take advantage of theseextra resources and to provide real-time updating of data and functions.

RMML macro documents 104 are text documents that contain routines justas RDML data is contained in a text document. This document contains theheart of the calculation: the specification of operations on numbers,such as a formula, an ordered list of other macros to perform, or listof instructions.

RDSL style sheets 106 act as templates for output reports. The RDML dataobject (discussed below) in the RDML data viewer 100 can be placed intoa report using one or more different style sheets. RDSL, a fullycompliant implementation of XSL, allows a data publisher to providemultiple report formats for its data. They are reusable in that a stylesheet written for one RDML data document 102 can be used for another ifthe specified restrictions are met. For example, a style sheet for atime-series data set can be used for another time series data set. Thestyle sheet editor 222 is basically a report-writer because the user cangraphically compose a report from a sample document, specify the typesof RDML data documents 102 that this report can apply to, automaticallycreate a style sheet 106 when the result is acceptable, and then use theresulting style sheet to create a report from any qualifying RDML datadocument 102.

The RDML search engine 224 searches RDML documents 102 similarly to theway HTML search engines search HTML documents. HTML search engines pickup key words, but can only tell a user that a particular documentcontains the requested word(s). They cannot, however, provide queryservices. For example, a user may wish to search the Internet for “allfinancial statements of computer services companies which have revenuegrowth>10%,” and the RDML search engine 224 provides this capacity. TheRDML Search Engine 224, however, does not index only keywords like theHTML approach, but also the element names and key attributes. Thispermits searching for numerical values, or posing complex queriesregarding the content and/or context of the data. The RDML search engine224 thus acts as a generalized query processor for RDML data document102, RMML macros 104, and RDSL stylesheets 106. Some aspects of thesearch engine 224 are described in greater detail in co-pending U.S.Provisional Patent Application Ser. No. 60/183,152, filed on Feb. 17,2000.

As mentioned earlier, each view 108 in the RDML data viewer 100 isessentially a separate application denoted on FIG. 3 as various RDMLPlug-in applications 225. The chart view, for example, is a separatecharting application that has been “plugged in” to the RDML dataviewer's basic infrastructure of Internet browser, XML parser/processor,RDML transformation and manipulation objects, internal object managementarchitecture, interfaces to other applications, and graphical userinterface (described below). For example, a mapping component can beplugged into the panel in which the chart is seen. Subsequently, when auser clicks on a line item, the colors of the different countries orstates will change to show a thematic map, or different dots willappear, etc. The RDML data viewer 100 may be designed in modular fashionto permit changing or adding component applications to leverage off thecommon components.

IV. System Details

With further reference to FIG. 3, several of the components (excludingRMML and RDSL components) are described in greater detail below. Theexisting databases 230 may be relational databases, object-orienteddatabases, or any other type of database. RDML tags in RDML documents102 add documentation to the types of pure data found in relationaldatabases. Since the data that already exists in relational databasescan be used to create RDML documents 102, the data may be made availableto either the RDML formatter 216 or the RDML server 218 and be in a flatfile format (rows and columns).

For connections, both the RDML formatter 216 and the RDML server 218read Open Database Connectivity (“ODBC”) and JDBC database sources. Theflat file aspect is based on the idea that RDML documents 102effectively model a basic row and column matrix. To produce an RDMLdocument 102, therefore, the original data source may provide a singletable, or create one with a query. Relational linking is possible withRDML documents 102, through a server to a relational database, orindirectly through hyperlinks to other RDML documents or hyperlinks toRDML document servers 218. This is similar to many databaseapplications: data is collected from various underlying tables to createa single table or screen to show the user. The data table to be used asa source for an RDML document 102 may be oriented to have the fields beone of three basic exemplary RDML data table types: time series,category, or X-Y plot described below.

With reference to the RDML formatter 216, once there is a flat file datatable of data points in the existing database 230, an RDML document 102can be created by adding tags that contain documentation regarding thedata table. The information contained in these tags are maintained in aseparate data table from the original data points. The RDML formatter216 is an application that assists a user in selecting the properdocumentation tags, saves the tags in a separate database (the RDMLimage database 226), and creates the actual RDML document 102.

FIG. 4 is a screen shot that shows how the RDML formatter 216 assiststhe user in “tagging” data, i.e., adding metadata that applies to theline items. In one implementation consistent with the present invention,for each line item of data, there are at least 18 different potentialattributes (described in detail below) applied using the radio buttons402. When a user selects a radio button 402, the formatter 216 suppliesa description 404 of the selected attribute. Upon selection of a radiobutton 402 from the left-most box, the user is presented with a list ofthe possible values in the middle option box 406. The user may eitherdouble click one of the options to add it as an attribute of theselected line item, or type in a new value in the text box at the top ofthe middle option box 406. The formatter 216 automatically updates theline item table 408 which, in this instance, displays the line items'ID, title, format and Y-axis title (attributes which are discussedbelow).

FIG. 5 shows a screen shot of the database tab and document managementscreen accessed by a tab 502 on the RDML formatter 216. This screenmanages RDML documents 102 that can be created from a relationaldatabase 230. The user can specify a list 504 of data tables in arelational database and have the RDML formatter 216 create RDMLdocuments 102 for each using default properties. From that point, theRDML formatter 216 is used to modify the defaults. The user may use theRDML formatter 216 to select tags from scratch (as shown in FIG. 4) fora document 102, but this puts an unnecessary burden on the user toremember which properties are appropriate.

The formatter 216 references a database 230 (shown on FIG. 3) specifiedby the documentation URL 506. The database 230 holds a list of datatables, and the formatter 216 inserts a table 504 that holds storesinformation regarding the data tables into the database 230 for laterreference. This table 504 is referenced by the documentation table name508. Similarly, the formatter 216 stores a list of line item attributes408 for the database 230 in the database which are referenced by theli_data URL 510.

The RDML image database 226 contains documentation that relates to aseparate set of data records in the existing database 230. The RDMLformatter 216 creates and maintains the RDML image database 226. TheRDML image database 226 standardizes the process of documenting datadocuments, and provides a controlled vocabulary for the metadata. TheRDML image database 226 also performs document management and tracking,update and version control, error checking, input validation, and thecreation of status reports.

The image database 226 contains a list of RDML documents 102 that it canproduce. The original data may be in flat files, relational tables, or atable that results from a query on a relational database. The imagedatabase 226 contains document metadata that references the originaldocument table or flat file in the original database 230. Documentationinformation contained in the image database 226 is added to this data.It further includes line item set metadata for the set of line items,documentation that is typically of a more technical nature and appliesto the line item set as a whole. Examples of such information is tabletypes, field definitions (“x values”) and hyperlinks that apply to theline item set as a whole. (A line item set may be generally analogous toa table; it is a collection of line items, which are analogous torecords in the database world.)

The image database 226 also includes line item metadata that referencesthe individual records of the original document table or flat file inthe original database 230. There may be a pointer from each line item'smetadata record to the corresponding record in the original data table.Each line item includes the fields of the original record, plus, in oneimplementation consistent with the present invention, at least 18additional fields that contain “attribute” documentation: object types,unit designators, hyperlinks, footnotes, and so forth. A listing ofexemplary attributes of a line item is described below.

FIG. 6 illustrates steps used by the data viewer 100 when accessing theRDML document server 218. The RDML server 218 occupies a middle positionbetween a database server 230 and a user's data viewer 100 or webbrowser. Although one architecture for RDML is to have RDML documents102 served from disk-based text files, users may sometimes wish tocreate RDML documents dynamically in response to queries. The tasks ofexecuting the query and delivering a result in RDML document form areperformed by the RDML server 218. To do so, a user submits the datarequest to the server 218 via the data viewer 100 (step 602). The RDMLServer 218 is a server application called by a web server (not shown)which fields the user's request. The RDML server 218 queries thedatabase 230 using known techniques (step 604), and the database returnsthe results to the RDML server (step 606). The server 218 then createsan RDML document 102 (step 608) and returns the RDML document to the webserver which transmits the results to the viewer 100 (step 610).

The RDML document editor 220 permits users to edit the actual elementsand attributes of an RDML, RMML, or RDSL document (102, 104 and 106).The documents may be presented in a tree view for selection and directediting. A text-based window may display the contents of the selecteddocument for editing. Besides basic editing, it performs a number ofutility functions: (1) search and replace, (2) validation, (3)well-formedness testing, (4) hyperlink validation, (5) cut-and-paste ofelements, and (6) replacement of elements with defaults.

IV.A. Internal Data Viewer Architecture

FIG. 7A depicts a schematic diagram of the internal architecture andprogram flow of the RDML data viewer 100, and FIG. 7B depicts themeaning of each symbol type in FIG. 7A. For each numbered component, adescription is given which provides further details on that component'sinput and output, internal decision process, storage format, objectarchitecture, and program flow.

Before fully describing FIG. 7A, however, it is important to understandan overview of the steps involved, which is depicted in FIG. 8 anddiscussed in conjunction with FIG. 7A. FIG. 8 is a flowchart describingsteps in a method for downloading, processing and displaying a RDMLdocument 102 in accordance with the present invention. FIG. 8 describesan overview of the steps involved, and each related component issubsequently described in further detail with relation to FIG. 7A.First, the RDML reader 704 finds and receives an RDML document 102 intext form formatted according to the structure of the RDML DTD 702 (step802). The RDML Reader 704 may be a class that runs in a separate threadand has methods for checking the RDML document 102 type (Time Series,Category, XY) and handling errors. The RDML Reader 704 then calls theXML parser 706 which parses the text (step 804). The RDML processor 708receives the parsed text from the XML parser 706, error checks it andcreates an object based on the data and structure in the received text.(step 806).

The RDML processor 708 transfers the resulting object to the X-valuetransformer 710 which performs type-checking and manipulates the fields(x-values) of the data so that it may be displayed and stored coherentlyand simultaneously with other active objects of the same type (step808). The X-value transformer 710 makes sure that the data values to begraphed against the x-axis are in common units. For example, if documentA is an annual time series and document B is a quarterly time series,the X-value transformer 710 in this case would use the “li_aggregation”attributes of the line items in document B to aggregate four quarters ata time into annual data. As a second example, if document A is acategory document with x-values equal to stock ticker symbols (F, IBM,XON, etc.), and document B contains x-values denominated in companynames (Ford, International Business Machines, Exxon, etc.), then thex-value transformer 710 will use the “li_class” attributes in the lineitems of each document to match them up. The X-value transformer 710sends the object to the primary data store 712 (“PDS”) for storage withother active objects of the same type (step 810). The views (716, 720,724 and 725) then display and present information using data from theactive objects in the PDS 712 (step 812).

Details of the steps and components involved are now discussed inconjunction with FIG. 7A. Described first is an RDML document 102defined by the RDML Document Type Definition. Description of the varioussoftware components of the data viewer 102 follows.

The data and metadata of an RDML document 102 may be formatted insidetags which denote the beginning and ending points of each data element.The element tags may also include attributes to be applied to the dataelements, a description of what sub-elements may be found within anelement, and vocabulary choices for different attribute values.

A full sample RDML data document 102 is shown at Appendix B. Shown belowis a fragment of an RDML document 102 that supplies the data for oneline item in the document. Note that element tags are designated withinangle brackets (“<” and “>”), and that attributes are listed that can beapplied to the data.

<line_item   li_ID = “1”   li_legend = “Department of Energy”   li_title= “Outlays − Dept. of Energy”   li_cat = “”   y_axis_title = “$ inThousands”   level = “1”   format = “#,##0;(#,##0)”   relation =“Parent”   li_notes = “”   li_desc = “”   li_prec = “−3”   li_unit = “$”  li_mag = “3”   li_mod = “in”   li_measure = “”   li_scale = “”  li_adjustment = “”   li_aggregation = “”>  <data_y> 2754567, 2699717,2726457, 2578954, 2343297, 2252927, 2474440, 2392904, 2392536, 2200326,2298612, 2303643, 2233062, 3229510, 3840973, 5049308, 6412986, 7441295,7261157, 11756883, 11657178, 10590471, 10991261, 10587245, 11026443,10692802, 11166039, 11386923, 12083898, 12478820, 15522633, 16941547,17839298, 17617000, 16203000, 14467000, 14366000, 15240000, 15190000,14938000, 14412000, 14556000  </data_y> </line_item>

In this example, the 18 lines with an “=” are “attributes” of the<line_item> element, and essentially, the attributes providemachine-readable documentation for the data values specified in thesub-element <y-values>. This particular line item describes “Departmentof Energy outlays in thousands of dollars,” but the specifics of the setof attributes are described below in conjunction with the RDML DocumentType Definition 702 which describes the structure and elements of a RDMLdocument 102.

RDML documents 102 may be produced by an ordinary text editor, by theRDML data formatter 216, or by the RDML data server 226. (XML browsersother than the RDML data viewer 100 are able to do little more than echothe text input to the user's screen since they cannot interpret the RDMLtags.)

IV.A.1. Document Type Definition

FIG. 9 graphically shows elements of the RDML Document Type Definition702. In one implementation consistent with the present invention, RDMLdocuments 102 conform to the rules provided by the DTD 702 (also shownon FIG. 7). In accordance with one implementation of the presentinvention, an RDML DTD 702 is shown at Appendix A. Attributes andelements of the DTD 702 may also be seen in the full sample RDMLdocument 102 in Appendix B. Those two Appendices A and B are useful forexamining specific attributes and elements of the DTD 702.

The DTD 702 data structure is optimized to provide information that isneeded in order in which it is required, to reduce the learning requiredon the part of new users to RDML formatting, and to avoid unnecessaryduplication. The first line of the DTD 702 in Appendix A starts with“<?xml encoding=“UTF-8”?>” because all XML documents start with a linethat tells the client application, in this case the data viewer 100,what type of document it is and the version of XML.

With further reference to FIG. 9, the DTD 702 used to define RDML datadocuments 102 is structured in a hierarchical tree structure ofelements. Each element may include a list of attributes (displayed inAppendix A, but not shown on FIG. 9) and/or an association with one ormore sub-elements. The DTD 702 specifies which attributes are requiredand which are optional for any embodiment of the DTD. Depending ondesign constraints, the required and optional elements may vary. At thehighest level, the DTD 702 has two elements descending from a rootelement, <rdmldoc> 902. The first element, <rdmldoc_header> 904,contains the metadata for the document as a whole and the second,<line_item_set> 906, contains the set of the line items.

In one implementation consistent with the present invention, the<rdmldoc_header> element 904 contains several attributes itself, and theoptional sub-elements <data_source> 908, <formatting_source> 910,<rdml_source> 912, <license_terms> 914, and <link_set> 916, eachdescribing some aspect of the source of the data. In thisimplementation, the <rdmldoc_header> 904 element may include tenattributes describing document information as a whole. These attributesare “rdml_doc_ID,” “doc_title,” “timestamp,” “version,” “expiration,”“freq_of update,” “num_line items,” “num_datapoints,” “x_indexes,” and“first_li_with data.”

The rdml_doc_ID attribute is the unique identification of the RDMLdocument 102 and is typically a file name or URL. The doc_title is aplain language description of the document that will appear at the topof reports and views for the document for use by a user. The timestampis typically generated by the application that created the document andmay denote the time that the document was created or the time the datawas accessed for creation of the document. The version describes whichvariant of the RDML document 102 it is and may be named by the creator.The expiration describes the date and time that the data in the document102 may no longer be relied upon, typically when the next update isexpected to be released. Freq_of update describes how frequently thedocument is updated and may be used by applications that want toschedule updates to the data. The next two attributes, num_line itemsand num_datapoints, are integers describing the total number of lineitems and number of data values respectively. These attributes areoptional and may be used as a “checksum” by a receiving application toensure that the data has not been accidently changed or corrupted.

The next field, x_indexes, denotes three data fields to use asrepresentative data fields in the tree view 720 (described in detailbelow). X_indexes is a comma-delimited string of three integers, each ofwhich is an index to a selected field. For efficiency, the indexes maydenote the end of the list of fields so that, for example, “−3,−2,−1”shows the last three fields in the tree view 720. Indexes based on theend are useful because most people reading a time series want to see themost recent data. Along, similar lines, the first_li_withdata attributeis an integer index that points out which line item is to be displayedon the chart when the document 102 is loaded into the data viewer 100.

The <data_source> 908, <formatting_source> 910, <rdml_source> 912,<license_terms> 914 elements, sub-elements of <rdmldoc_header> element904, may optionally contain one or more of sub-elements of<contact_info> 918 which contains contact information. This element canbe used by the target application to create an email letter, update acontact list, or populate a database of information sources. The sameelement structure is used for all contact information sub-elements 918so that the application that created the document 102 only has to createone structure.

In one implementation, this contact information is represented by elevenattributes: “role,” “name,” “company,” “address,” “city,” “state,”“zip,” “country,” “email,” “form,” and “comments.” Role is the roleplayed by the party in the creation of the document, i.e., “data source”for the <data_source> 908, “formatting_source” for the<formatting_source> element 910, etc. “Form” determines whether thehyperlink is a “simple” link or “extended” link. Under the Xlinkspecification, a language designed to implement links between XMLdocuments and resources, hyperlinks may be simple or extended. Xlink isdescribed in “XML IE5 Programmer's Reference,” Alex Homer, Wrox Press,1999, which is incorporated herein by reference. Simple links aretraditional “jump” hyperlinks in which clicking on that link will closethe current page and open the target page. Extended links areapplication-specific and can identify different types of resources, suchas multimedia files and other non-document resources.

The contact information in the <data_source> 908 describes who or whatcollected the data to create the original database, while the sameattributes in <formatting_source> 910 describe who or what added theRDML tags to the original data to create the RDML document 102. The sameinformation in <rdml_source> 912 describes the person or company thatcreated this particular document and made it available to the outsideworld.

In addition to the <contact_info> 918 sub-element in <license_terms> 914which describes the contact information regarding the licensing of theinformation, the <license_terms> element has its own set oflicensing-related attributes. These attributes include:“copyright_cite,” “holder,” “license_type,” “warranty,” “disclaimer,”“terms,” “date,” “email,” “state,” and “country.” The copyright_cite isa string that may appear on reports regarding ownership of theparticular data set in the RDML document 102. A typical example might be“Copyright 2000, e-Numerate Solutions, Inc. All Rights Reserved.” Theholder attribute lists the full legal name of the owner of thecopyright. License_type lists the type of license, such as“none—proprietary and confidential,” “public domain,” “pay per use,”etc., and terms lists the payment terms, if any, such as “$1 perdownload.” The information in these attributes may be used by routinesassociated with the RDML processor 708 to automatically track andimplement licenses and payments.

Another sub-element of the <license_terms> element 914 is the <linkset>element 916 which, in one implementation, has two attributes and its ownsub-element <link> 922. A <linkset> 916 is a collection of hyperlinks.These hyperlinks may be either HTML files or RDML files. The individual<link> elements 922 hold the actual links and attributes. The <linkset>element's two attributes are form, described above, and href, a standardstring for URL or web address, and they designate the HTML or RDML pagewhere a page of hyperlinks may be found. This is useful when the creatordoes not want to list all of the hyperlinks in the document 102 itself.

The <link> element 922 describes hyperlinks to other documents andcontains, in one implementation, nine attributes: “form,” “href,”“behavior,” “content-role,” “content-title,” “role,” “title,” “show,”and “actuate.” These link related attributes are described in the XMLIE5 Programmer's Reference, pp 95-97. The title is a string that appearsin the application as a hyperlink title. For example, in an HTMLbrowser, it will appear as highlighted, underlined text. Actuatespecifies when the link should be traversed—when the resource that thelink points to is retrieved or accessed, and show specifies how thetarget resource will be displayed. Behavior specifies instructions thatcontrol the behavior of the link in the way that the content isdisplayed or the link is traversed, and role describes what role thetarget resource plays in the link. Content-role and content-title arealternative places for the title and role, but are not specified inXlink standards.

Finally, <rdmldoc_header> 904 may have its own <linkset> 916 having<link> elements 922. RDML allows users to attach hyperlinks to differentelements such as an entire document, a particular line item, or otherelement in the RDML document 102. The reason for the multiple placesthat hyperlinks may be placed is so that the user can view in one placeall the links that apply only to the element under consideration. Forexample, an RDML document 102 may contain the data for a company'sfinancial statement. The creator of the document may decide that certainlinks apply to the whole company (links to product lines, competitors,etc.) and that others only apply to single line items (such as a linkattached to the “Equipment Leasing” line item that points to thefootnote for that line item or an accounting regulation applicable tothat account). Even though they are attached to different elements, thelinks may have the same form. Another reason for multiple linksetelements is to facilitate keeping links together with their logicalowners.

Continuing to refer to FIG. 9, on the line item side of the <rdmldoc>902, the <line_item_set> 906 which contains information on thecollection of line items in the RDML document 102 also contains severalattributes and several elements. These attributes include:“line_item_set_type,” “time_period,” “character_set,” “missing_values,”“null_values,” “zero_values,” “dates_values,” and “percentages.”

The first attribute, the line_item_set_type, is, in one implementation,an important attribute which classifies the line item set into one ofthree types: time series, category (or cross tab), and x-y plot.Generally, the “type” in this context is the characterization of thex-axis values and whether they represent a time series, acategorization, a x-y plot or other. These line item set types aredescribed in detail below in connection with the x-value transformer 710which manipulates line items of the same set type. Generally, line itemsets of different line item set types may not be actively manipulatedtogether. If the line item is a time series, valid lengths in thetime_period attribute may be years, quarter, months, days, etc.

Character_set designates which standard character set is represented,thereby allowing for support for foreign languages. Missing values holdsa designator for the numerical value that represents a missing value,because many views of the data, in particular chart views, need to knowwhich numbers represent blanks. Otherwise, a blank might be interpretedas “0.” Null_values designates the character to be treated as null sothat it is not confused with “not applicable,” or “missing” or “0.”Finally, zero_values designates characters that should be interpreted as“0,” and not “null,” “missing,” “not applicable,” etc.

The <line_item_set> 906 has, in one implementation, several sub-elementsincluding <data_x> 924, <li_class_set> 926, <linkset> 916, and one ormore <line_item> elements 928. At the line item set level, metadataregarding line items as a set is shared among all the line items so thatthe data need not be repeated. In particular, the <data_x> element 924contains field information common to all line items in the line itemset. The <data_x> element 924 includes the x-values and informationregarding the x-values of the line items in the set of line items in theRDML document 102. For example, if the line item set is a time series,the x-values may represent the years, months or other timelines (e.g.,1990, 1991, etc.) listed across the bottom of a chart with which all ofthe data is associated. Because this information is the same for eachline item in the line item set, it is only included once in the RDMLdocument 102. In one implementation, in addition to the actual x-values,<data_x> 924 also contains the following attributes: “x_title,”“format,” “x_notes,” “x_desc,” “x_prec,” “x_unit,” “x_mag,” “x_mod,”“x_measure,” “x_scale,” “x_adjustment,” and “x_links.”

In <data_x> 924, x_title is the title displayed on the x-axis as thedata is displayed on a chart. Format is a string providing a templatefor the default representation of the x-axis values. The strings arethose familiar from spreadsheet programs (examples may also be seen onFIG. 4):

#—digit(s), zeros suppressed

0—digit(s), zeros displayed

.—decimal point

,—separator

A-z, other characters—displayed literally.

Other formatting codes can also be used (e.g., codes used in scriptinglanguages). X_notes may contain miscellaneous footnotes regardingx-values of the line item set, while x_desc may describe additionaldescription regarding the x-axis values.

The x_prec attribute describes the precision or number of significantdigits for purposes of axis label display. In this attribute, negativenumbers cause rounding of amounts greater than zero. For example, aprecision of “2” will display a number as “8,254.43”. That same numberwith a precision of “−2” will be displayed as “8,300.” The underlyingrepresentation of the number will be the full value; only the formattingand representation on the screen will change. The data viewer 100 usesthis primarily for formatting the axis labels, but the attribute isavailable for default formatting as well in other uses such as reports,footnotes, etc.

The subsequent attributes, x_unit, x_mag, x_mod, x_measure, x_scale, andx_adjustment, represent the meaning of the x-values and are used by thedata viewer 100 for manipulation, reconciliation and display with otherRDML documents 102. In RDML, numbers are collectively described by theseattributes which describe the numbers' units. They are as follows:

Unit: the physical unit of the numerator

Magnitude: the size of the numerator

Modifier: relation of the numerator to the denominator

Scale: the size of the denominator

Measure: the physical unit of the denominator

Adjustment: special qualifier (i.e., inflation adjusted)

For example, a line item reported to represent “$ in thousands permillion people” can be represented as:

$\frac{\left\lbrack {1\mspace{14mu} \$ \; {US}} \right\rbrack*\left( {1,000} \right)}{\left\lbrack {1\mspace{14mu} {person}} \right\rbrack*\left( {1,000,000} \right)}$

Therefore, the attributes of the line item are:

-   -   Unit: $US    -   Magnitude: 1,000    -   Modifier: /    -   Measure: 1 person    -   Scale: 1,000,000

Access to these attributes for line items provides enormous power to thedata viewer 100. It facilitates the interpretation and transformation ofthe numbers. It allows multiple lines to be placed on a single chartwithout conflict and allows macros to be applied without the requirementof human intervention to answer questions about the units. It furtherallows reporting templates to make automatic adjustments to provide themost readable reports. In particular, the data viewer 100 uses theseattributes to construct y-axis labels and descriptors when the user hasmade a transformation and the “y_axis_label” attribute is no longerappropriate.

A standard vocabulary for units and measures may be used for efficiency,and magnitude and scale may be more simply represented as a power of 10,e.g., 3 for thousands, 6 for millions, etc. This permits more rapidtransformations and eliminates potential confusion of variant usages andspellings (e.g., million, mille, MM, etc.)

For an example of the use of these attributes, suppose the RDML dataviewer 100 has plotted the following value/measurement:

-   -   426 US Dollars (in thousands) per Hour, adjusted for inflation        (1996=100).

The user now wants to convert this to:

-   -   “X” Italian Lira (in billions) per Day, in nominal lira

where “X” is the value to be calculated and the rest of the line is themeasurement. The data viewer 100 makes this transformation automaticallyfor the user because it has conversion factors for the following:

RDML Attribute: Begin: End: Conversion factor: Unit US Dollar ItalianLira A* 0.0000234 Mag Thousands Billions A* 1,000,000 Mod per per A* 1Scale Hour Day A* 24 Measure  1 1 A* 1 Adjustment Adjusted for infl. Notadjusted A* annual factor Value 426 1.189

The data viewer 100 multiplies the conversion factors (or performs anyother appropriate mathematical operations) to manipulate the display.The user does not have to look up each of the conversion factors,marshall them into the correct sequence, do the arithmetic, and makecorrections such as rounding adjustments. The user may simply select anew unit, magnitude, etc. from a drop-down box and make a selection.

FIG. 10 illustrates steps used by the data viewer 100 to manipulate thenumerical information in an RDML document 102 to produce a desiredtransformed display. First, the data viewer 100 locates the RDMLdocument 102 (step 1002). The document may be located either locally oronline using a URL, the search engine 224 or any other technique. Next,the data viewer 100 selects and accesses the desired document 102 (step1004). The data viewer 100 then accesses the line item that needs to betransformed (step 1006) and determines the desired transformations (step1008). The desired transformations may be received from a user or may bedetermined by the data viewer 100 automatically to, for example,accommodate the addition of a new document 102 to a display of a currentone. The data viewer 100 accesses the unit, magnitude, modifier, scale,measure and adjustment attributes of the document or line item to betransformed (step 1010). Using these attributes, the data viewer 100determines the conversion factors, if any, for each (step 1012). Theseconversion factors may be stored locally or retrieved online over anetwork 214. The data viewer 100 then multiplies the conversion factorsto transform the numerical data into the desired display (step 1014) anddisplays the transformed line item or document (step 1016). If more thanone line item is to be displayed, the data viewer 100 may repeat thesesteps so that all appropriate line items may be transformed to thedesired display format (step 1018). Similarly, if more than one document102 needs to be transformed, the steps may be repeated for eachdocument. In this way, documents 102 having different numerical sets maybe automatically manipulated for simultaneous display or quicktransformation of display format without human intervention. The systemautomatically resolves conflicts between different documents indifferent formats by transforming them into one desired form.

In one implementation, when the system converts one unit to anotherunit, it converts the original source unit to a base unit known by thesystem, and then converts the base unit to the target unit. The systemstores conversion factors from base units to other units in a unit listXML file, a portion of which is shown at Appendix C. For instance,suppose the base unit used by the system for length is “meters,” andnumerical values are to be converted from “yards” to “miles.” The viewer100 converts the yards to meters using the stored conversion factor, andthen from the meters to miles using the appropriate stored conversionfactor. In this way, the unit list file need only contain conversionfactors from the base unit to various other units, and need not list aconversion factor for every possible combination between various units.

The structure of the unit list file is as follows: a <unitlist> elementis the root, and it has one level of child nodes, each of which is a<unit> element. The unit elements each have a number of attributes andelements that describe the characteristics of that unit necessary toconvert it into another unit or set of units.

The conversion element contains the attributes necessary for making aconversion where the source unit and the destination unit are both ofthe same type. For example, converting “miles” to “inches” is simply amatter of finding the correct multiplier to apply to the number ofmiles, because both units are measures of type “length.”

The conversion element contains six elements: (1) “conv_target”describes the target unit of measurement that the following conversionfactors will bring you to, (2) “conv_factor” is the number to multiplyby the source value to arrive at the destination value, (3)“conv_constant” is the constant to be added to the product of the sourcevalue and the conversion factor. For example, in the conversion formulafor Fahrenheit to Centigrade (F=32+9/5 C), 32 is the “conv_constant”,(4) similarly, if the conversion involves a logarithmic conversion, thenecessary factors are included in “conv_log”, (5) “conv_source” is adescription of the standards body that set forth this particularconversion factor, and (6) “conv” href′ contains the URL for theapproving standards body.

The type element contains one of the following text strings: (1) Length(base unit=meter), (2) Area (base unit=square meter), (3) Volume (baseunit=cubic meter), (4) Mass (base unit=gram), (5) Time (baseunit=second), (6) Temperature (base unit=centigrade), (7) Energy (baseunit=joule), (8) Currency (base unit=$US), (9) Compound (no base unit),(10) Diverse (no base unit), (11) Collection (no base unit), and (12)Occurrences (no base unit).

The Compound and Diverse types are constructed from one or more of thebasic units. Compound types are simple combinations of others. Example:“miles per hour” is a combination of a length unit and time unit. Inorder to convert a Compound type into another type, it is necessary tobe able to make the necessary conversions of the decomposed units.

Diverse types are those that are constructed of descriptions. Forexample, an “ohm” is an electrical unit described as “the resistanceoffered to an unvarying electrical current by a column of mercury at thetemperature of melting ice, 14.4521 grams in mass, of a constantcross-sectional area, and 106.3 centimeters in length.”

A Collection type is a collection of persons, places, things, etc. Forexample, a data series denominated in “people in millions” means thatone unit of this type is a collection of one million people. Collectiontypes can use any of the conversion elements. For a simple conversionexample, suppose there are 2.4 people per family in a sample. Then“people” could be converted to “families” by a simple division by the2.4 conversion factor.

An Occurrence type is a collection of events. “Cycle” would be anOccurrence type that could be divided by “seconds” to produce a compound“cycles per second” unit of measurement.

The “subtype” element is for finer distinctions among types. The“plural” element is for constructing new titles, legends and labels atthe completion of a conversion operation. An “alias” element is providedfor enabling conversions where data has been entered in a common, butnonstandard form. For example, tables often use “in” instead of“inches.” The “desc” element is provided so that a plain languagedescription can be given the user. The “icon” element provides a placefor giving the unit an icon to be used in lists, drop-down boxes, etc.

Referring back to the elements and attributes of FIG. 9, in <x_data>924, there is an x_links attribute which may be a comma-delimited stringof URL's for linking to other sources.

In addition to this element, the <li_class_set> 926 element representsthe set of line item class elements and, in one implementation, has noattributes but has one or more sub-elements representing line itemclass, <li_class> 930. These line item class tags specify categories invarious classification systems to which the numbers belong, such as “<USDollars>” or “<Total Revenues>”. The data viewer 100 uses these classtags to select which macros can apply, to adjust report formats, and tomake the correct selections of assumptions in analytic processing. Theclass designations permit validation and conforming of different datasets, thereby allowing the data viewer 100 to combine documents fromunrelated sources into a single unified source. Class tags may be usedby macros that look at the class tag list to see if it qualifies to acton the particular line item. For example, if a line item in a financialstatement is tagged as of the class “debt,” the macro knows that it canuse this line in calculating “debt-to-equity” ratios. But if the lineitem is tagged “piano,” for instance, the macro will not be applied.Note that, in this implementation, the element names for the classes areentered as comma-delimited strings.

The <li_class> element 930, in one implementation, has five attributes.These are “class_name,” “parent_class,” “form,” “href,” and“description.” Class_name is the name of the class to which the lineitem set belongs, and parent_class denotes the name of the parent class.These attributes may be used by more advanced features of the dataviewer 100 such as the macros.

The <line_item_set> element 906 further contains a <linkset> 916 similarto the previously described <linkset>. As before, this <linkset> 916further has a <link> element 922 previously described.

The <line_item> 928 element may have, in one implementation inaccordance with the present invention, four sub-elements and 18attributes. The elements are <data_x> 938, which contains the x-valuesfor this line item if they are different from the default x-value in theline_item_set element <data_y> 932 which contains the y-data values, thedata numbers or values of the line item, a <linkset> 916 having a <link>922 as previously described, and a <note_set> element 934. The <noteset>934 contains one or more <note> elements 936 which have user readable,plain language notes regarding the line item.

The attributes of the line item include: “li_ID,” “li_legend,”“li_title,” “li_cat,” “y_axis_title,” “level,” “format,” “relation,”“li_notes,” “li_desc,” “li_prec,” “li_unit,” “li_mag,” “li_mod,”“li_measure,” “li_scale,” “li_adjustment,” and “li_aggregation.” Severalof those attributes have the same meaning as attributes previouslydescribed except that they specifically describe only the line item andy-values to which they are attached.

The li_ID is a unique identification number for the <line_item> element928 and may be numbered from 0 to n (where n is the number of line_itemelements). In one implementation consistent with the present invention,the numbers are unique and in order.

The li_legend attribute is a plain language string describing the lineitem that does not need to be unique. Generally, it appears in theleftmost column of the views. The li_title is a string defining thegeneral subject of the line item. In the data viewer 100, this may beused as the title of the chart and as titles in reports. Typically,titles are the same for line items grouped together, but they are notrequired to be.

The li_cat attribute represents a line item category. As opposed to theli_legend and the li_title, which are displayed on the chart in the dataviewer 100, the li_cat is not normally displayed. It is generally anon-printing designator for a category that the line item might belongto. Often, this may be a table name, or a primary key in a database, orsome other organizing identifier. It may be used to group line items forreports.

The y_axis_title attribute is a string which will appear on the y-axisas the title of that axis. However, if the user applies a transformationto any variable in the descriptor, this hard-coded y-axis title will bereplaced by one generated by the data viewer 100 using other attributes.

The level attribute and relationship attribute specify hierarchicalrelationships between line items. Conventional links in relationaldatabases are maintained by matching records on the basis of “keyfields.” One drawback of this approach is that nothing is known aboutthe character of the relationship except that it exists, and there is noway to tell, absent specific documentation elsewhere, that one record isa child or parent of the other, and whether that nature is acontainment, a derivation, and inheritance, etc. In RDML, the creator ofthe data may specify the hierarchical level of each line item and thenature of that hierarchical relationship. The data viewer 100 uses thelevel attribute and the relationship attribute to create a hierarchicaltree, to place icons representing the relationship in front of each lineitem to summarize the derivation of numbers and describe their context,and to assist macros and updating data tables. The level attributespecifies how many levels down from the parent node a line item is,while the relationship attribute specifies the nature of therelationship, such as whether the line item is a child of another lineitem or contained by another. It may also determine whether the lineitem is an additive or subtractive subcomponent of a parent, or asubtotal that is dependent on other child line items. These previouslymentioned attributes and elements make up a DTD 702 in accordance withmethods and systems consistent with the present invention.

Li_aggregation is an attribute useful if a user wants to “aggregate” or“deaggregate” data based on differing x-axis transformations. Thisattribute explains to the data viewer 100 how to handle this particularline item when such transformations are attempted. For example, if aline item set presents bank account information, each line item may be atime series and presents quarterly data, but the user may wish to seethe data on an annual basis. For some line items in the set, it issimply a matter of summing up four quarters worth of data (e.g.,deposits) in which case the attribute value would be “sum,” but forother line items (e.g., closing balance), only the last quarter's valueneed be shown, in which case the attribute value would be “last.”Similarly, if a minimum annual balance is desired for four quarters ofminimum balances, only the lowest balance for all four quarters would beneeded. Such a line item's li_aggregation attribute value would be“minimum.” Possible accepted values include: “sum,” “average,”“minimum,” “maximum,” “first,” “last,” and “none.”

IV.A.2. Reader, Parser and Processor

With reference back to FIG. 7A, the RDML reader 704 may be an objectwithin the RDML data viewer 100 which manages the process of finding anRDML document 102 (locally, on a LAN, or on a Wide Area Network such asthe Internet), passes it to the XML parser 706, relays error notices tothe user, and coordinates the updating of other components states toreflect a rejected or damaged RDML document 102. The user of the RDMLdata viewer 100 may initiate the download of an RDML document 102 inmany different ways including: clicking on an RDML hyperlink (these arelike any other hyperlink, except that the target document may end in“.rdm”), typing a “.rdm” URL into the “Address” box of RDML data viewer,or requesting the loading of the document in a macro. Also, whileconventional HTML browsers have a cache of only HTML documentsrepresented as the “history” of the browser, the browsers may onlydisplay one of these documents at a time. Given an URL address, the RDMLreader 704 reads in Document Object Model (“DOM”) compliant documents(e.g., RDML documents 102), discussed below. The XML reader 704 may beimplemented by a third-party set of Java classes, such as the XML4Jparser developed and licensed by IBM, but others may also be used. TheRDML reader 704 may cache multiple documents in RAM if they arecompatible with the active data set. Not only are these documentsimmediately available, but sub-elements of the documents are availableimmediately because the data viewer 100 may maintain indexes ofimportant data and metadata in the documents. Additionally, macros maybe used to find specific elements in the document that is read in by theRDML reader 704.

The XML parser 706 takes a serial stream of text characters from theRDML data document 102, performs basic functions such as eliminatingwhite space, dividing input into words and groups of words and searchingfor opening and closing characters (primarily “<” and “>”). The XMLparser 706 used in the RDML data viewer 100 may also be a third-partyset of Java classes, such as the XML4J parser developed and licensed byIBM, but other parsers may also be used.

The processor 708 receives the parsed text and creates a tree-shapeddata structure of the data elements, matching the structure of the RDMLDTD 702 hierarchy. The hierarchical structure conforms to the DOM Model,meaning that data is available in a standard form, and that a standardlibrary of methods and functions are available for accessing data,editing elements, searching through nodes to find certain elements, andso forth. The XML DOM standard is controlled by the World Wide WebConsortium, and can be found at “http://www.w3.org/TR/REC-DOM-Level-1/”.

The RDML Processor 708 generally performs three primary functions on theincoming parsed text to create an internal software object: errorchecking, structuring, and adding functionality. The error checkingfunctions of the processor 708 simply compare the output of the parser706 against the text expected as defined by the DTD 702. If the incomingdocument does not conform, the processor 708 determines whether thedefect is: (1) not critical, in which case a warning is sent to a logand work continues, or (2) critical, in which case work stops and anerror message is sent to the routine that called the parser 706.

The structuring function is a matter of assembling the text into ahierarchical data structure matching the hierarchy described in the DTD702. The target data structure may be a vector of vectors, or othercollection of collections. When the data structure is created, it is“wrapped” in a software object (an “RDMLDoc” object) that adds aninterface to the data so that other software objects can communicatewith it. Most of the added functions (“methods”) provide access tospecific subsets of the data or particular elements or attributes.

The functions of the RDML processor 708 can be performed by the sameclass as the RDML Reader 704, where the RDML reader 704 has been set upon a “callback” relationship with the XML Parser 706. In that way, whenthe parser 706 gets a new element from the RDML document 102, it informsthe RDML reader 704 that it found the element and returns it to thereader. In such a way, the RDML reader 704 acts as a processor as wellas reader (even though it may hand off the actual element handling toanother class).

IV.A.3. X-Value Transformer and Line Item Set Types

Regarding the X-value transformer 710, the term “X-value” refers to thefact that the fields of the input data records are plotted along thex-axis of the chart view 716 by default. (The values of each record foreach field are plotted on the Y axis.) For example, a time series will,by default, be plotted in the chart year with the time periods plottedon the x-axis. When more than one data document is input, their datafields must be correlated before they can be presented together in acommon view. The X-value transformer 710 determines what adjustmentshave to be made, and then accomplishes them.

Generally, the RDML data viewer 100 recognizes three different types ofline item sets (i.e., (1) “time series,” (2) “category,” and (3) “X-YPlot”) which account for the majority of end user tables. The X-valuetransformer 710, by recognizing these types, can automatically providethe correct display and transformation routines, saving the user thetime and expense of changing a broad range of details. To give anexample of this, when a times series table is encountered, the dataviewer 100 can recognize that the x-values must fit the permissibletypes of dates, check them, conform them, and format them, thus sparingthe user the work. In one implementation consistent with the presentinvention, a line item set type is a required attribute of the line itemset element 906.

FIG. 11 shows the steps used by the X-value transformer 710 to store anew document in the primary data store (“PDS”) 712 described below.Generally, the X-value transformer 710 determines whether a newly inputdata document is of the same type as the one(s) currently stored in the“active documents” list of the PDS 712. Active documents are availablefor display in the tree view 720, to be charted, to be added to thespreadsheet view 724, and so forth.

First, the X-value transformer 710 receives a new document 102 (step1102). It then determines the type of the active documents in the PDS712 (step 1104). If the newly arrived document is the same line item settype as the active documents (step 1106), it is added to them in the PDS712 (step 1108). If it is of a different type than the currently activedocuments in the PDS 712, the user is notified that it does not matchthe currently active documents (step 1110). The user may choose toreject the new document 102 (step 1112), in which case the object is notadded to the PDS 712 (step 1114). If the user chooses to erase thecurrently active documents (step 1116), the currently active documentsare erased (step 1118) and the new one is loaded (step 1120). Otherwise,the new document 102 is placed in the PDS 712 as a “standby” document(step 1122). Standby documents are available for providing data toscripts and macros, but do not interfere with the active document views.Optionally, if the x-value transformer 710 need not perform anytransformations, the RDML reader 704 may store the document in the PDS712.

If the newly arriving document is of the same line item set type as theactive documents, the X-value transformer 710 matches the data_x fieldsof the new document to the existing documents. They may be in adifferent order, may be spelled differently, be in a different form, orotherwise not immediately compatible. The X-value transformer 710 makesthe necessary adjustment according to the type of line item set. Forexample, time series line item sets have elements which are ordered intime. One obvious incompatibility is that periods may be different.Often, one set of data is in years and the other in, for example,months. The X-value transformer 710 uses attributes of the line items tohandle each correctly. However, monthly data cannot just be added up toproduce a yearly value, for example, because the number might representa non-additive value. For example, a line item might be “Ending BankBalance,” but adding up 12 monthly ending balances does not produce ayear-ending balance. The line item provides a period-length attributethat specifies that it is a “period-end” value, and the X-valuetransformer 710 uses the last month only to create a yearly value. Inanother example, monthly “deposits” would be added together, and monthly“average interest rate” might be a “period-average.” Each line itemprovides instructions on how it is to be handled in conversion to otherperiods; this is provided by the li_aggregation attribute.

Another change that might be made is in the date format. Some data setsmight simply display the year (“YYYY”), others might use a standard dateformat (“YYYY-MMDD:HHMMSS.MSS”), or some other variant. The X-valuetransformer 710 puts these all into a common form.

The data viewer 100 additionally provides tags describing how it is tobe handled in the event of a period widening/shortening, or a periodshift. Numbers may be tagged as “sum,” “median,” “average,” “lastvalue,” “first value” or a specified formula. The X-value transformer710 and the data viewer 100 may also handle “period shifts,” a relatedtype of conformance. For example, a first data source may be based on acalendar year ending on December 31 while a second data source is basedon a fiscal year ending on September 30. The RDML data viewer 100 mayuse the period_length attribute of the x_data element 924 to designatethe period length of the data, in conjunction with the li_aggregationattribute of the y_data element. The latter attribute is used toestimate a conforming transformation.

Y-values, the data values in a line item, may change when the x-valueshave been conformed. For instance, if twelve months of “average interestrate” is aggregated to produce “annual average interest rate,” theupdated designation of the number that will appear in legends or axistitles changes. The data viewer 100 recognizes that the resulting valuesmay possibly undergo a transformation based on unit, magnitude,modifier, scale, measure, and adjustment attributes. These attributesallow efficient and automatic interpretation, translation, manipulationand presenting of data in a line items. They further facilitate theautomatic changing of text descriptions in charts and reports to beautomatically changed by macros.

Additionally, to conform differing time periods in separate documents,the X-value transformer 710 and the data viewer 100 may prompt userassistance if needed. For example, a first data source may bedenominated by fields such as “Week 1,” “Week 2,” etc., while a seconddata source is denominated by “Apr. 4, 1999,” “Apr. 11, 1999,” and soforth. The X-value transformer 710 recognizes this problem (and a broadset of similar circumstances), and presents a dialog box asking the userfor the actual date that “Week 1” begins on.

The Category line item set type is a common type of line item set thatis often referred to as a “crosstab.” In this line item set type, thex-values are categories. On a chart, for instance, the x-axis may bedivided into eight categories for eight companies, with the y-axisshowing the values of revenues or profits. Sometimes matching the fieldsof different source documents by name is too dependent on wording,spelling, or language to permit efficient matching. The challenge forcategories line item sets is to handle these differences in usage. Forexample, company income statements may start with a concept of “sales,”but the actual words used may be “revenues,” “total revenues,” “grossincome,” or any other designation used in different languages, dialects,or industry-specific terms. To handle these line item sets, the X-valuetransformer 710 lines up categories from multiple data sets by firstmatching up any actual matches in spelling (ignoring cases in thedefault). Second, it looks at the class elements 930 to see if there arestandard vocabulary tags; these standards may be different for differentindustries or uses. When dealing with companies, for example, the tickersymbol may be used as the matching tag. For instance, one data set mayhave a category for “Ford” another for “Ford Motor Company,” and anotherfor “F.” All would be matched by the common presence of a tag <“F”>(Ford's ticker symbol) in the class element 930. If this fails toprovide matches, the data viewer 100 presents the user with a dialog boxwith two lists of fields. Using “drag and drop” techniques, the user canquickly match the two sets of fields, and fields with no match aresimply appended as new fields. In addition to creating a mappingdictionary based on text, class sets, and user input, the data viewer100 can use a mapping file specified by a user or an input document tocombine files automatically.

FIGS. 12A, 12B and 12C depict screenshots of an X-Y plot 1202 inaccordance with the present invention. Most commonly found in scientificstatistical series, an X-Y plot 1202 by its nature treats every x-valueas distinct. This display plots individual data points on the graph. TheX-value transformer 710 is only required for collating only exactmatches. The screenshot also displays a tree view 720 that correspondsto the data in the X-Y plot 1202 and a legend 1204. As shown on FIG.12A, the X-Y plot 1202 displays the selected line item 1206, and thelegend 1204 changes as the line item selection changes. The FIGS. 12Band 12C show the X-Y plots 1202 resulting from the selection ofdifferent line items 1206 in the tree view 720.

IV.A.4. Primary Data Store

FIG. 13 depicts a primary data store 712 and some objects which itstores. The primary data store 712 is a cache of loaded RDML documents102 that may be implemented in a number of ways (e.g., as a vector, as adictionary or hash table, or as some other collection of objects).

Once the X-value transformer 710 has determined an active or standbystatus for a newly arrived data document 102, and made any necessarymodifications to the x-values, it passes a new RDMLDoc object 1302 tothe PDS 712, which manages its communications with the various views orplug-in applications. This PDS 712 central storage allows the differentviews (716,720, 724, and 728) to have access to an object 1302representing the original source data. The individual views (describedbelow) make their own copies of the portions of the data that they need,and in whatever transformed form they require. The PDS object 712generally does not perform transformations on data; it simply holdsthem, adds and removes them, and makes them available in a publicinterface to other objects. Table 1 below shows an exemplary classdiagram of the PDS object 712. Note that vectors are used to hold theRDML documents 102 in this implementation; it would also be possible touse a hash table or collection data structure.

TABLE 1 PrimaryDataStorage −Active_RDMLDocs : Vector −Active_RDMLLines :Vector −Standby_RDMLDocs : Vector −Standby_RDMLLines : Vector+Add_RDMLDoc(rdmldoc : RDMLDoc) : void +Add_RDMLLine(rdml_li :RDMLLineItem) : void +getRDMLDoc(rdmldoc : RDMLDoc, Status : int) :RDMLDoc +getRDMLLineItem(rdml_li : RDMLLineItem, status : int) :RDMLLineItem +getNumRDMLDocs( ) : int +getNumRDMLLineItems( ) : int+clearRDMLDoc(rdmldoc : RDMLDoc) : void +clearRDMLLineItem(rdml_li :RDMLLineItem) : void

In the class diagram, the upper section lists the object's variablenames followed by their types. The lower section lists the method nameswith the argument name and type in parentheses followed by the methodoutput type. As shown, the PDS 712 provides variables and methods forstoring active and standby RDMLDocs 1302 and RDMLLineItems 1304. The PDS712 object includes methods to add, retrieve and clear documents andline items, in addition to methods for determining the number ofdocuments and line items.

An RDMLDoc object 1302 is a full internal representation of the RDMLdocument 102. It contains as its central attribute the tree-structureddata elements contained in the document's original tags and implementsthe DOM interface. Applications that work with DOM objects may also workwith RDMLDoc objects 1302. The RDMLDoc object 1302 provides a higherlevel interface for the different views of the RDML data viewer 100. TheTable 2 below shows a class diagram of an exemplary RDMLDoc object 1302in accordance with the present invention.

TABLE 2 RDMLDoc −txDoc1 : txDocument +RDMLDoc( ) : RDMLDoc+createDoc(filename : String) : TXDocument+getAttributeValue(elementname : String, attributeName : String) :String +getAttValue(lev1_tag : String, lev2_tag : String, lev3_tag :String, att_name : String) : String +getData_xDefaults( ) : JCVector+getLinkAttValue(element : String, index : int, attname : String) :Atring +getLinkText(element : String, index : int) : String+getNumLineItems( ) : int +getNumLinksForElement(elementname : String) :int +getRDMLLineItem(att_name : String, att_value : String) :RDMLLineItem +getTXDoc( ) : TXDocument +makeRDMLLineItem(li : Node) :RDMLLineItem +parseCommaDelimString(in : String) : JCVector+setTXDoc(txDoc_in : TXDocument) : void +traverseDOMBranch(node : Node): void

Described below are class methods shown in Table 2 of an RDMLDoc object1302 in accordance with one implementation consistent with the presentinvention. First, RDMLDoc( ) is a constructor for creating an internalRDMLDoc object 1302. The method “createDoc” reads in the file indicatedby an input URL, parses it, and creates a new TXDocument which the userthen usually assigns to this RDMLDoc object 1302. A TXDocument is anobject which implements the Document Object Model (DOM) interface. TheTXDocument creates the DOM structure for the file and “wraps” it withvarious access and administrative methods. It is the DOM-compliantoriginal representation of the document. The “setTXDoc” method sets theunderlying TXDocument, and initializes object properties such as thenumber of line items, and “getTXDoc” returns the underlying TXDocument.

Whereas an RDML document 102 forms a tree of elements having attributeswith values, the “getAttributeValue” method returns the attribute valuesfor the named element, and “getAttVal” returns as a string the attributevalue found at an inputted element name and attribute name. The“getLinkAttValue” method gets the attribute value of a hyperlinkelement, according to the element name and attribute specified and“getLinkText” gets the corresponding hyperlink text.

When called, “getNumLineItems” returns the number of line items in theRDMLDoc 1302 and similarly “getNumLinksForElement” returns the number oflinks for an element.

The “getRDMLLineItem” method supplies the first RDMLLineItem 1304(described below) based on the value of a particular attribute. Forexample, specifying “li-ID” and “3” will return the RDML Line item inwhich the “li-ID” attribute equals “3.” The method called“makeRDMLLineItem” takes the indicated node, assigns it to a newRDMLLineItem object 1304 and initializes the object.

The method “getData_Defaults” returns a vector of the default x-values.Furthermore, “parseCommaDelimString” takes a comma-delimited string asinput and returns the values between commas as elements of a vector andreturns a vector of the strings. Finally, “traverseDOMBranch” takes aninput node as a parameter and then traverses from that node downwards,and at each node, an operation, such as finding an element with aparticular name, may occur.

Similar to the RDMLDoc object 1302, the “RDMLLineItem” 1304 is an objectthat provides high-level methods for retrieving data on a line item, anyassociated links or notes, and the attributes. The views of the RDMLdata viewer 100 work with RDMLDocs 1302 and RDMLLineItems 1304 to createtheir presentations. Table 3 shows a class diagram for an exemplaryRDMLLineItem object 1304.

TABLE 3 RDMLLineItem −data_x : TXElement −data_y : TXElement −jcvdata_x: JCVector −jcvdata_y : JCVector −li : TXElement −line_item_set_att :NamedNodeMap +RDMLLineItem( ) : void +get_jcvData_X( ) : JCVector+get_jcvData_Y( ) : JCVector +get_strX_Value(index : int) : String+get_strY_Value(index : int) : String +getAttributeValue(attributeName :String) : String +getLinkAttribute(index : int, attName : String) :String +getLinkText(index : int) : String +getNumDataPoints( ) : int+getNumLinks( ) : int +initLineItem(doc : RDMLDoc, lineitem : Node) :void +set_li(input : TXElement) : void

Described below are class methods shown on Table 3 of an RDMLLineItem1304 in accordance with one implementation consistent with the presentinvention. Methods with the same name as described above in connectionwith the RDMLDoc object 1302 have the same general function although,since a line item is already specific to an element, the methods takedifferent arguments because they typically do not need an elementspecified in the given arguments.

RDMLLineItem( ) is a constructor that creates an RDML LineItem object,and “initLineItem” initializes the line item to the values found in theRDMLDocument. The method “get_jcvData_X” d “get_jcvData_Y” return the x-and y-value vector for the indicated number of the line item. The“get_strX_Value” method and “get_strY_Value” return the x- and y-valueat the number of the line item in the x_values vector as a string.

The “getNumDataPoints” method is called to receive the number of datapoints, i.e., the number of x-values, in a line item. The method“set_li” allows the calling routine to set the line item in the RDMLdocument 102 that this particular RDMLLineItem is to represent.

Referring back to FIG. 7A, in one implementation consistent with thepresent invention, the chart manager object 714 takes up to sixRDMLLineItems 1304 from the PDS 712 and displays them on a chartdisplayed on the graphical user interface 734 and is typically used inconjunction with the tree view 720 and the macro panel 732. When a userclicks a mouse on a line item in the tree view 720, that line item isadded to the chart. When the user clicks the mouse on a macro line inthe macro panel 732, the selected line items that are charted aretransformed according to the programming of the macro. The chart manager714 may be separated from the graphical chart view 716 to allow theability to change chart software components easily should different orbetter graphic chart components become desirable.

Views

The data viewer 100 presents the user with a number of different views(716, 720, 724, and 728 as shown on FIG. 7A) which the user may use toview the information in RDML documents 102 stored in the PDS 712. Theseviews include a chart view 716, which shows graphical charts and graphsof the data, and a tree view 720 showing hierarchical representations ofline items. Additionally, the data viewer 100 presents a spreadsheetview 724 which shows a data sheet similar to a spreadsheet, and afootnote view 728 which shows the text of footnotes associated with RDMLdocuments 100. The views are discussed in detail below.

IV.A.5. Chart View

Upon receiving RDML markup documents, the chart view transforms,formats, manipulates and displays data stored in the markup documentsusing the attributes describing the meaning of the data. The chart viewuses the attributes of the numbers to, for example, facilitate thesimultaneous display of different series of numbers of different typeson a single chart and automatically display appropriate descriptivetextual components.

As an example, the chart view automatically determines when a firstseries is in the “U.S. dollars” and the second series is in “Frenchfrancs”; it may automatically place them on separate axes orautomatically translate the units. It can also determine the titles forthese axes and set the labels on the axes. The chart constructs itselfautomatically using the attributes of the individual elements of themarkup document, and these actions may be initiated with a single mouseclick.

FIGS. 14A-F depict the chart view 716 in the top half of the screen, andthe tree view 720 in the lower half. The chart view 716 has two primarycomponents: the chart itself and the chart legend 1402. The line item1206 that has been selected in the tree view 720 is automaticallygraphed in the chart 716. The chart manager 714 generally has threeprimary responsibilities: (1) collecting messages from the tree view720, macro panel 732 and main menu (not shown) regarding changes to maketo the chart 716, (2) obtaining the correct line items or macros fromthe PDS 712 or the macro manager 732, and coordinating transformationsto the data, and (3) managing the chart's data object (the “chart data”object 715), which contains the data in the form in which it will beused in the chart, and the attributes of those line items.

Generally, the chart manager 714 handles updates and manipulations tothe chart itself (e.g., axes, labels, etc.) while the chart data object715 handles the plotting of the data on the chart 716. The chart managerobject 714 provides the information the chart data object 715 needs toupdate its internal data structures. Chart data 715 is a data model thatis used by the central graphical chart 716 to paint itself, but othercomponents also use the data: the footnotes, the chart legends andtitles, and any macros that are operating on the data.

One way to visualize the role of the chart manager 714 (and its datapartner, the chart data object 715) is to view the steps of a method ofa complete sample scenario: the user has selected a line item 1206 inthe tree view 720 and the chart manager 714 is notified that this lineitem is to be added to the chart 716. There are various ways to set upthe chart data/chart manager architecture. One way described in detailbelow is to create the chart up front and then feed it changes in data(initialization, clearing, updating data series, etc.) A second generalapproach is to use the data to create a new chart upon every request fora change.

FIGS. 14A-F will now be described in greater detail, and in particular,FIGS. 14A and 14B will be described in connection with FIGS. 15A, 15B,and 15C, which illustrate steps of a method for updating a chart view716 upon the selection of a line item 1206 in the tree view 720 in anexemplary scenario in accordance with the present invention. FIG. 15Aillustrates steps mainly involving the tree view 720 and graphicalinterface 734, while FIGS. 15B and 15C illustrate steps mainly involvingthe chart data object 715 and chart manager 714 respectively.

As illustrated in FIG. 15A, a user selects a line item 1206 in the treeview 720 on the graphical interface 734 (step 1502). The tree view 720obtains the ID of the selected line item 1206 (step 1504) and removesany old macros that are applied (step 1506). The chart manager 714 thendeletes the last series (displayed data of a line item) from the chartview 716 to make way for the newly selected line item (step 1508).

Referring now to FIG. 15B, the chart data object 715 removes existingdata from the chart 716 (step 1512). It then obtains the RDMLDoc object1302 from the PDS 712 (step 1514) and the RDMLLineItem object 1304 fromthe RDMLDoc object (step 1516). After doing this, the chart data object715 normalizes the x-value data (step 1518). For example, if one chartedseries displays data from 1961 to 1998, and the new one displays datafrom 1973 to 2005, the chart data object 715 ensures that the chartdisplays data from 1961 to 2005. The chart data object 715 then fillsthe x-axis 1404 with data (step 1520) and fills the y-axis 1406 withdata (step 1522).

As shown in FIG. 14B, a chart may have more than one y-axis 1406 chartedat a time, (i.e., a different y-axis on either side of the chart) todisplay multiple line items simultaneously. Thus, the chart data object715 further marks which y-axis the series is on (step 1524), and if itis on a Y2 axis 1408 (a second y axis) (step 1526), it adds that axis(step 1528). The chart data object 715 sets the number formats for theaxis labels 1406 and 1408 (step 1530) and sets the number precision(step 1532). Finally, it updates the footnotes (step 1534) and runs anymacros that are applied (step 1536).

Referring now to FIG. 15C, the chart manager 714 then sets the Y1 title(step 1538) and the Y2 title (step 1540) using line item attributes.After that, it updates the series styles (step 1542), the chart title1410 (step 1544), the legend 1402 (step 1546), and the x-axis 1404 (step1548). After these updates, and the chart manager 714 updates the numberprecision (step 1550), the y-axis 1406 (step 1552) and the chart types(i.e., area, bar, stacked bar, line, pies, points, etc.) (step 1554).Subsequently, it updates the footer 1412 (step 1556) and sets themaximum x-value to the extent of the last used value, disposing ofblanks on the right side of the chart 716 (step 1558). Finally, thegraphical interface 734 repaints the graphical chart 716 with the newlycreated updates (step 1560).

The chart manager 714 and chart view 716 can chart different seriestypes on a single chart and handle transformations automatically.Because two (or more) data series may be placed on the chart 716 fromdifferent source documents 102, they are synchronized for purposes ofplacing them on the common graph. The chart manager 714 uses data_xelements or the metadata tags to automatically transform data to permitdifferent series types to appear together on a chart. It recognizes, forexample, when a first series is in “US Dollars” and a second series isin “French Francs”; it makes arrangements automatically to place them onseparate axes. There is no need for the user to go through a charting“wizard” or to find, understand, and translate the various units,titles, and adjustments. One click on each of the series' lines in thetree view 720 (potentially with a modifier key (e.g., the CTRL key)depressed) instructs the chart view 716 to construct itself given themetadata of the individual elements. The chart manager 714 and chartdata object 715 consider and take into account the following in updatingthe chart: the unit type, magnitude, scale, modifier, measure, y-axistitle, chart title, chart footnote, precision, number format, chart type(line, bar, etc.), legend and colors of the various components.

The data viewer 100 also permits the adding of a series to a chart usinga single click or command. Adding a series to a chart increases thenumber of series displayed on the chart. In conventional spreadsheets,charting programs, and data graphical interfaces, this task requires theuser to either rebuild the whole chart through the wizard, fill in adialog box with information on the new series, or add the numbers bycustom programming. When the data viewer 100 adds the new series to thechart with a single mouse click. The existing data is maintained as itwas, and any necessary changes to the chart's type, format, scale, etc.is made automatically by the chart manager 714 and chart view 716 toaccommodate the new series.

Just as a series can be added with one mouse click (or one command fromthe menu), so can it be removed. There is no need for the user to worryabout accidentally deleting something, as no actual information is lostfrom the data viewer 100. It can always be added back to the chart 716with a simple mouse click.

The chart view 716 also supplies an expandable legend 1402 as shown onFIG. 14A. A significant problem for most users of spreadsheet programshas been the inability of the user to control the size, format, andhandling of the legend 1402. The result is that charts usually end upwith legends such as “MSFT” and “SUNW,” rather than longer descriptionswith multiple colors and fonts, word-wrapping and other readabilityenhancements. The chart view 716 chart provides legends that (1) cangrow to unlimited sizes, (2) support word-wrapping, (3) can containmultiple fonts, (4) can contain multiple font types (bold, italics,normal), and (5) can contain varying colors for emphasis. If the legendinformation (typically stored in the li_legend attribute) for a lineitem is too long for the legend box on the chart, the information mayword-wrap and scroll to accommodate the additional information.

The chart view 716 permits further convenience by automaticallyspecifying the y-axis title 1414. Current spreadsheet and chartingprograms require the user to provide a y-axis title, usually through achart wizard or by specifying a location to look up a title. The RDMLshifts this burden to the data originator, who is in a better positionto accurately specify the description of the y-axis values. The y-axistitle 1414 specified by the data originator is placed in an attributefield (y_axis_title) of the line item element tag and is used by thechart view 716 as the default y-axis title 1414 when the line item isadded to the chart view 716.

Often, however, the user wants to make a change to the numbers anddisplay the transformed series on the chart 716. In this case, thedefault y-axis title 1414 may no longer be correct. Rather than requirethe user to manually figure out what the new value description is (aprocess that could take several minutes or longer with current analyticprograms), the chart manager 714 and chart view 716 data automaticallygenerates a new y-axis title 1414 upon transformation of values usingthe information provided in the modified unit, magnitude, modifier,scale, measurement, and adjustment attributes of the line item 1206.

For example, suppose a first series is charted as “$ in Millions,” andthe user applies a macro that divides every number in the series by1,000. The chart manager 714 automatically creates a new y-axis title1414 of “$ in Billions.” Number transformations can lead to quitecomplicated transformations of the y-axis title 1414. A user maymultiply a first series (“Gallons in Millions”) by a second series (“US$ per Gallon”); the result will be a series of numbers, a third series(“US $ in Millions”). If there are ambiguities, the data viewer 100presents the user with a dialog box displaying all the known informationregarding the quantities involved and requests that the user supply atitle.

Similarly, the chart manager 714 and chart view 716 can automaticallygenerate the x-axis title and chart titles 1410 using the metadataattributes. In addition to generating y-axis and x-axis titles, the dataviewer 100 automatically performs the task of creating a new chart title1410 when the charted series are changed or when multiple series areadded to the same chart. For example, a first series has a default charttitle of “Total Sales,” a second series has a default chart title of“Total Expenses,” and a third series has a default chart title of “TotalSales.” The data viewer 100 will create a combined chart title of “TotalSales; Total Expenditures” by combining the dissimilar elements, andeliminating the duplicate elements.

Three examples illustrate other types of automatic title manipulation.In the first example, suppose a chart has two series placed on it:Series A has a title of “GDP” and a legend of “China”, and Series B hasa title of “GDP” and a legend of “Malaysia”. If both are put on thechart, the titles will duplicate each other. In one implementationconsistent with the present invention, duplicate titles are removed suchthat the title for this chart will be simply “GDP”. Because the serieslegends are different, the legend on the side of the chart will have twoentries: “China” and “Malaysia”.

As a second example, suppose the legends are duplicative: Series A has atitle of “China” and a legend of “GDP”, and Series B has a title of“Malaysia” and a legend of “GDP”. Because both legend entries would be“GDP”, there may be confusion about which legend applies to which lineon the chart. In this case, the data viewer 100 transposes the legendand chart title entries such that the result is the same as in the firstexample above; the title of the chart is “GDP” (the duplicate isremoved) and the legend entries are “China” and “Malaysia”.

Finally, in a third example, suppose the series have different titlesand different legends. Series A has a title of “GDP” and a legend of“China”, and Series B has a title of “National Savings” and a legend of“Malaysia”. The legends are left as is, and a new chart title is createdby appending one to the other separated by a “;”. The chart title on thedisplay thus becomes “GDP; National Savings”, and the first legendbecomes “GDP—China” and the second legend becomes “NationalSavings—Malaysia”. All three of these changes are string manipulations(selecting and/or appending).

The chart manager 714 and chart view 716 can also automatically trimbeginning and ending x-values 1404, thus relieving the user of the needto trim null leading and trailing values from charts. In conventionalspreadsheet and charting programs, chart pointers must be recreated ormanually adjusted when the underlying data is enlarged or shortened. Forexample, if a series is charted that runs from 1990 to 1998 and it isreplaced by data from 1990 to 1996, there would be two blank spaces atthe right side of the chart. The data viewer 100 and chart manger 714avoid this and similar problems by handling missing or null values atthe front or back of line items as indications that the chart should beautomatically restructured.

The chart manager 714 also automatically formats the x- and y-axislabels 1404 and 1406. RDML shifts the burden of formatting the numberson the x-axis 1404 and y-axis 1406 from the user (of which there may bethousands or millions, each reformatting the numbers manually one ormore times) to the data originator (of which there is one, who only hasto do it once.) The format templates are regular expression stringsfound in current spreadsheets and programming languages. The data viewer100 uses the formatting strings for the axis labels on the chart view716, for the numbers in the tree view 720, and as defaults for thenumbers in reports. The formatting templates are automatically changedif a macro moves the numbers outside of the precision range that islegible on the chart 716, or out of a format that makes sense in thetree view 720 or in a report.

As stated previously, one of the RDML line item element attributes isthe precision of the number, the number of significant digits to bedisplayed in a chart. Unlike conventional products, which leave thisentirely up to the user to figure out, the data viewer 100 uses thespecified precision to set the scale of the y-axis 1406, and the formatand precision of its labels and tick marks.

Additionally, the chart manager 714 automatically creates and removes asecond y-axis 1408 as shown on FIG. 14B. A chart with two dissimilarseries plotted on it will require two axes. The y-values may not be ofthe same units, measures or scales. A user might, for example, haveplotted a series denominated “$ in Millions” and then want to add to thesame chart 716 a series denominated “% of GDP,” and these two seriescannot share a common y-axis. Chart manager 714 recognizes thisincompatibility, creates a new y-axis 1408, and directs all subsequentformatting, macros, etc., to the proper axis. Current spreadsheets andcharting programs require that the user restructure the chart with acharting wizard (entailing many directives to be entered, and, muchtrial and error to get the various scales, colors, etc., correct), or bycustom programming. The data viewer 100 automates this process, creatingand formatting a new axis if required by the specifics of the unit andscale attributes of the line items. If the series is removed from thechart, the associated axis is removed and the various scales, colors,etc., of the remaining series are updated to make the chart readableimmediately.

Table 4 shows a class diagram of the chart manager 714.

TABLE 4 ChartManager −chart1 : JCChartComponent −chart_data : ChartData−chart_legend : ChartLegend −chart_title : JCTitle −CDV1 : ChartDataView−CDV2 : ChartDataView −DS : DataStore −LineColors : JCVector −mainFrame: MainFrame −series1 : ChartDataViewSeries −series2 :ChartDataViewSeries −x_value_labels : JCVector −xaxis : JCAxis −xtitle :JCTitle −y1axis : JCAxis −y1title : JCTitle −y2axis : JCAxis −y2title :JCTitle −yLabelGenerator1 : YLabelGenerator −yLabelGenerator2 :YLabelGenerator +addSeries(key : String) : void +addY2Axis( ) : void+ChartManager(mainFrame : MainFrame, chart_comp : JCChartComponent,legend : ChartLegend) : void +checkYAxisTitle(series : int, y1title :JCAxisTitle, y2title : JCAxisTitle) : int +deleteLastSeries( ) : void+deleteSeriesAfterFirst( ) : void +getAddSeriesFlag( ) : boolean+getChartData( ) : ChartData +getYAxisTitle(series : int) : String+initChart( ) : void +markWhichYAxis(num_series : int) : void+replotChart( ) : void +replotSeries( ) : void +resetChart( ) : void+setAddSeriesFlag(flag : boolean) : void +setChartType(type : int) :void +setDataStore(ds : DataStore) : void +setStartPeriod(sp : String) :void +updateChartTitle( ) : void +updateChartTypes( ) : void+updateFooter(num_series : int) : void +updateFootnotes( ) : void+updateLegend( ) : void +updatePrecision( ) : void+updateSeriesStyles(num_series_local : int) : void +updateXAxis( ) :void +updateYAxis(num_series_local : int) : void

Class methods of a chart manager object in accordance with oneimplementation consistent with the present invention are describedbelow. ChartManager( ) is a constructor for the chart manager object714, and “initChart” initializes the chart to be empty, and“getChartData” gets the chart data object 715.

The method “addSeries” adds a series to the chart while“deleteLastSeries” removes the last added series. Similarly,“deleteSeriesAfterFirst” deletes all series beyond the first series.

A series flag is set to “true” if the next series is to be added inaddition to the already charted series. A “false” flag tells the chartto erase the last current series and replace it with the new series. Themethods “getAddSeriesFlag” and “setAddSeriesFlag” retrieve and set thisflag.

The method “getYAxisTitle” returns the y-axis title, and“checkYaxisTitle” checks the current y-axis title to see if the newlyplotted series is to be on the current axis, or if a new axis is to becreated. “AddY2Axis” adds a second y-axis to the chart if needed. Themethod “markWhichYAxis” tells the ChartData object which axis the newline item has been plotted on.

The method “resetChart” resets the chart to the state it was in when thedata viewer 100 started while “replotChart” updates the physical aspectsof the chart. Similarly, “replotSeries” replots a series due to changes.

The “setChartType” method tells the chart manager what chart type todisplay upon calling replotChart, and “setDataStore” tells the chartmanager what data store object 712 it will be dealing with. If the datais a time series, “setStartPeriod” sets the internal variable for thestarting period of the chart. Finally, the update methods each updatethe corresponding aspect of the chart in response to potentialmanipulations or changes, e.g., “updatePrecision” updates the precisionof the chart.

Table 5 shows a class diagram of the chart data object 715.

TABLE 5 ChartData −chtData : JCVector −chtHeader : JCVector −cm :ChartManager −originalPlottedYear : String −start_period : String−zeroData : String[ ][ ] +addSeriesToChart(ds : DStore, key : String) :void +decrementNumSeries( ) : void +deleteLastSeries( ) : void+deleteSeriesAfterFirst( ) : void +fillXAxis_CT(rdml_li : RDMLLineItem): void +fillXAxis_TS(rdml_li : RDMLLineItem, yearsDiff : int, sizeDiff :int) : void +fillYAxis_CT( ) : void +fillYAxis_TS(rdml_li :RDMLLineItem, start : int, yearsDiff : int, sizeDiff : int) : void+getAddSeriesFlag( ) : boolean +getChtData( ) : JCVector +getChtHeader() : JCVector +getChtHeaderElement(series : int, element : String) :String +getDataInterpretation( ) : int +getDataItem(row : int, column :int) : Object +getDifferencesInX(rdml_li : RDMLLineItem, yearsDiff :int[ ], sizeDiff : int[ ] : void +getName(series : int) : String+getNumRows( ) : int +getNumSeries( ) : int +getPointLabels( ) : String[] +getRow(row : int) : Vector +getSeriesLabel(series : int) : String+getSeriesName(series : int) : String +getStartPeriod( ) : String+incrementNumSeries( ) : void +normalizeValues(rdml_li : RDMLLineItem,xory : int, yearsDiff : int, sizeDiff : int) : JCVector+setAddSeriesFlag(input : boolean) : void +setChtData(jcvln : JCVector): void +setChtHeader(jcvln : JCVector) : void+setChtHeaderElement(series : int, element : String, value : String) :void +setDataItem(row : int, column : int, c : Object) : boolean+setNumSeries(new_num : int) : void +setOriginalPlottedPeriod(in :String) : void +setStartPeriod(in : String) : void +zeroChtData( ) :void

Below are class methods shown in Table 5 of a chart data object inaccordance with one implementation consistent with the presentinvention. Methods having names that are the same as methods in thechart manager are not described because they perform the same functionon the data alone.

The chart data object uses the methods “fillXAxis_CT,” “fillXAxis_TS,”“fillYAxis_CT,” and “fillYAxis_TS” to fill the x- and y-axes of timeseries and chart data sets. The methods “decrementNumSeries” and“incrementNumSeries” change a counter storing the number of series onthe chart.

The method “getChtData” returns a vector of chtData, which is a vectorof vectors: each element of the outer vector is a vector of data for oneline item. The “getChtHeader” method returns a vector of chtHeader,which contains a vector of header information for each line item. Thisvector is a list of the values of the attributes of a line item, e.g.,magnitude, title, etc., and “getChtHeaderElement” gets the value of aparticular element from chtHeader for the indicated series.

Operating on data sets, “getName” returns the data set name, and“getNumRows” returns the number of rows in the data set. The method“getRow” returns one row of a series while “getSeriesLabel” returns thelabel. The “getDifferencesInX” method aligns the time periods for timeseries charts, and “getNumSeries” returns the number of series in thenum_series variable. Many of the get methods have corresponding setmethods that set the value instead of receiving it.

The chtData variable is a vector of vectors (each sub-vector is the datafor one series), and “getDataItem” returns the data value in aparticular row and column of chtData. Used by the constructor,“zeroChtData” posts an empty chart. The “getPointLabels” method returnsan array of strings, each of which is a point label of chtData

For a time series, “getStartPeriod” retrieves the start period of thetime series, and “normalizeValues” normalizes values upon the additionof a series to the chart. The method “getDatalnterpretation” returnseither “array” or “general” to describe what form the data sourcestructure is in. (A returned value of “array” is for Times Series andCategory data—which share x values—, and a returned value of “general”is for XY data, in which X values are generally independent.)

IV.A.6. Tree View

Referring back to FIG. 14A, this screen shot further contains the treeview 720 on the lower half of the screen. The tree view 720 presents ahierarchical view of the data. The tree view 720 serves a differentpurpose than “datasheet view” of conventional spreadsheets and databasemanagement systems. It shows the numbers in their context visually. Theuser can see the dependency relationships, identify from icons andvisual clues how the different line items are related to their parents,peers, and children. The “Units” column 1416 prominently displays theunits, scales, magnitudes, etc., of each line item, an important displayin mixed data sets, where the unit context changes from line item toline item.

Each line item in the various active RDML documents 102 is displayed inthe original order. In the tree view 720, each RDML document 102 beginsa new top level node. The information displayed in the tree view 720 isa summary of important data from and about the line item, not a displayof all the data points as would be found in a typical spreadsheet view.Instead of presenting a potentially confusing matrix of raw data digitsthat make the discerning of patterns difficult, the tree view 720 shows,in one implementation, the following information for each line item:legend 1402, units 1416, three user-selectable representative datapoints 1418, and one or more summary columns 1420. In the example onFIG. 14A, there is some important documentation 1416 (description,units), some representative data 1418 (in this case, three years worth),and a summary data column 1420 (in this case, the sum of all the datapoints). The first column 1416 displays the legend of the line item.This is the plain language description; it is repeated in each viewwhere identification of the line item must be made by a human.

The representative data columns 1418 in the tree view 720 give the uservisual clues as the relative importance, the types, and the format ofthe line items. The RDML data viewer 100 permits the user to selectdifferent fields to be displayed. For example, one user might want tosee “1940, 1970, 2000” to get a sense of the long term trends, whileanother might only wish to see “1998, 1999, 2000” to see the recenttrends.

The summary column 1420 allows the user to choose a statistic that iseither desired to understand the lines and their context better, or thatis desired for purposes of sorting the columns from greatest to least orvice versa. Any of the columns can be sorted simply by clicking on them.The summary column provides much easier statistics for the user thandatabase or spreadsheet formulas because the RDML data viewer 100provides one-click selection of statistical methods, thus removing theneed to write formulas, adjust for missing values, handle nulls in thedenominators, etc. Some examples of summary statistics include: (1) sum,(2) average (3), median, (4) minimum, (5) maximum, (6) moving average,(7) variance/standard deviation, (8) % difference (selected periods orcategories), (9) % of parent, (10) % of specified line item, (11)correlation with parent, and (12) custom formulas. For each of thesestatistical measures, the RDML data viewer 100 provides a dialog box inwhich the user can adjust the assumptions. For example, the “movingaverage” can be for one period, five periods, ten periods, and so forth.

The tree view 720 emphasizes that line items are the primary data unitin the RDML data viewer 100, as opposed to single numbers as are foundin spreadsheets as cells. Since each line item 1206 is an object, theRDML data viewer 100 may be thought of as an object-orientedspreadsheet. The icons 1422 for each line item identifies that lineitem's context. For example, a “+” icon 1422 indicates that adding thatline item to its peers will produce the parent line item. This featureaddresses a shortcoming of spreadsheets and database datasheet views:the inability to view formulas and data at the same time. It shows theuser how the numbers are related to one another.

Conventional database management systems, spreadsheet and numericalanalysis tools have no built-in indication of how one record is relatedto another. In relational databases, the position or row may have norelevance to its data. RDML and the tree view 720 changes this by makingthe position of a line item in a set a usable piece of information by auser, and icons 1422 may visually designate the relationship of a lineitem to its parent node.

In one implementation consistent with the present invention, thefollowing values are used for relationship icons: (1) plus, (2) minus,(3) times, (4) divide, (5) equals, (6) computed at, (7) member, (8)collection, (9) child, (10) parent, (11) memo, (12) general, (13) note,(14) none, and (15) root.

Sub-line items may add up to the parent line item (or may be modified byother relationships of their sibling line items.) “Plus” may add tosiblings while “minus” subtracts from them. For example, a line itemcalled “Net Sales” may have two children: “Total Revenues” and “Cost ofGoods Sold.” If “Total Revenues” has an li relationship attribute of“PLUS”, and “Cost of Goods Sold” has one of “MINUS”, then the treeview720 can show that Net Sales is equal to Total Revenues minus Cost ofGoods Sold. “TIMES” and “DIVIDE” show multiplication and division ofline items respectively.

“EQUALS” is the same as “plus,” but shows the result of calculations ofline items above it in order. “COMPUTED AT” is used for assumptions,such as percentages, interest rates, etc., while “MEMBER” denotes thatthe line item is simply a member of a collection of line items denotedby the parent line item. In this case, no assumption is made regardingarithmetic relationship, if any.

“COLLECTION” denotes that the line item has child members one leveldirectly below it and denotes the concepts of sets or collections.“CHILD” illustrates that the line item is simply a “child” of the“parent” line item. It implies a sort of descent, derivation, orinheritance. No assumption is made regarding arithmetic relationship, ifany.

“MEMO” is a line item that might be of interest to those looking at thesibling line items, but which is not necessarily related to thesiblings, while “GENERAL” is a generic designator. “NOTE” is usuallyused for line items with text values, and “NONE” denotes that norelationship is implied. “ROOT” states that the line item is the rootline item.

The tree view 720 also provides other capabilities. It allows the userto chart multiple line items 1206 by holding down the “shift” key.Although number browsing can be done in the data viewer 100 with amouse, it is also possible for users to graph line items using arrowkeys. When the focus is on the tree view 720, navigating up and downwith the arrow keys automatically chart the selected line item 1206. Ifthe “shift” key is held down, the succeeding data series will be addedto the chart, rather than just replacing the previously selected series.

FIG. 14C shows that, in one implementation consistent with the presentinvention, when a user right-clicks on a selected series, a pop-up menu1424 is displayed showing the different types of documentationavailable. As shown in FIG. 14D, selecting “description” shows a window1426 containing information about the particular series, with theinformation being transferred from the tag form to a plain language,user-friendly format.

FIG. 14E shows that, in one implementation consistent with the presentinvention, the user may graph multiple line items simply by selectingdifferent “checkboxes” 1450 in line items in the tree view 720. In thisimplementation, the collection of selected line items is passed to thechart data object, which is then charted by the chart manager 714.

In one embodiment of the present invention, the selection of acontiguous set of lines that is less than all the lines in the tree view720 is facilitated through a series of mouse events. First, a mouse downevent is performed over a line (e.g., Bristol Center). The mouse is thendragged down (highlighting lines in the process) to the last line to beincluded in the group (e.g., Hamlet West Center). By delaying the mouseup event while retaining the cursor over the last line to be included,the user is able to signal the system (and the system is able to detect)that all elements in the selected/highlighted group are to be added.Accordingly, the system checks their corresponding check boxes.

The tree view 720 further provides an easy way of creating an RDMLdocument 102 through drag-and-drop techniques. In conventionalspreadsheet and DBMS applications, it is possible to create new tablesfrom existing ones by selecting the data rows and cutting and pastingthem, or by writing a SQL query. In the tree view 720, creating a newRDML document 102 complete with necessary documentation can be performedby dragging and dropping the desired line items to an icon thatrepresents the new document. Macros may also be created and manipulatedin the same manner.

The data viewer 100 may also set macros to be executed automatically asthe selected line items are changed. Known as “locking” of macros, thispermits browsing through data in a transformed state.

FIG. 14F shows that a line item may have a visual link associated withit that can be activated by a user. Upon activation of the link 1430, alist of associated hyperlinks 1432 is displayed for selection by theuser. The link 1430 itself may indicate the number of associatedhyperlinks 1432. The user may then select any of the hyperlinks toaccess the corresponding web site.

IV.A.7. Spreadsheet View

FIG. 16 depicts a screen shot that shows the spreadsheet view 724 in thelower half and the chart view 716 in the top half. The ultimate goal ofmany users is to get a set of numbers arranged into a format that willfit into an existing spreadsheet of theirs. While many programs offercut and paste transfer of numbers from a source application to a targetspreadsheet, such an approach still leaves the user with the task ofmanipulating, normalizing, aligning and transforming the data. Acut-and-paste operation is therefore usually followed by the manualrecalculation and retyping of every number. The RDML data viewer 100, bycontrast, allows the user to make the necessary data transforms withmouse-driven operations before loading the numbers into a spreadsheet.

Referring to FIG. 16, as line items 1206 are added to and subtractedfrom the chart view 716 or tree view 724, they are added to andsubtracted from the spreadsheet 724. In addition, any changes to thelines plotted on the chart view 716 (as the result of applying a macroor combination of macros) are immediately reflected in the numbers inthe spreadsheet 724. This provides one-click addition of information tothe spreadsheet view 724. Therefore, the way to copy data into thespreadsheet is simply to add them to the chart 716. It is also possibleto copy an entire data document 102 or collection of data documents fromthe tree view 720 to the spreadsheet view 724, making any desired macrochanges in the process.

Furthermore, RDML documents 102 may be created directly from thespreadsheet view 724. Whereas a data table is shown in the spreadsheet724 (either created from another RDML document 102 or typed in fromscratch), an RDML document may be created from that data in from thedefault specified by the user. This performs a task similar to an XMLeditor, but does so in a table format for the data, which is a morenatural way to enter tabular data, not in the tree structure of currentXML editors.

The spreadsheet view 724 may also directly read Internet data using aURL 1602. It will except formulas that use Xpointers (used by Xlink tospecify destination of a link) to read in data from remote RDMLdocuments 102. In this manner, data may be incorporated into a singlespreadsheet from a number of sources with no need to prepare query orprovide custom programming code.

As shown in the class diagram below in Table 6, the spreadsheet manager722 may be a simple object; the chart manager/chart data 714 and 716combination may be the actual repositories of the data. The chartmanager 714 feeds data to the spreadsheet manager 722, which places thedata in the correct cells. The spreadsheet manager 722 communicatesdirectly with a graphical spreadsheet object 724, which in the case ofthe RDML data viewer 100 may be a third-party component.

TABLE 6 SpreadSheetManager −gridControl : GridDataSheet −chartmanager :ChartManager +fillFromChart( ) : void

IV.A.8. Footnote View

FIG. 17 is a screenshot which shows the footnote view 728 in the lowerhalf. Generally, footnotes are a type of extended documentation thatoften get lost in transmitting and displaying numbers. Each line itemhas, as an attribute, a text string providing short footnotes which maybe accessed by a mouse click (that is, by clicking the “Footnotes” tab1702 at the bottom of the data viewer 100). As with the spreadsheet view724, the default value is for only the plotted series to have theirfootnotes displayed. However, it is possible to display all of thefootnotes of an RDML document 102 in the spreadsheet or style sheetreport views.

The footnotes in the footnotes view 728 are intended to be simple,important reminders about the data. Typically these include usualperiods (a fiscal year), adjustments, special problems and so forth. Bydefault, the footnotes view 728 also shows the source of the RDMLdocument 102 and the original underlying data. In one implementationconsistent with the present invention, anything requiring more than 255bytes is represented in an HTML page for which there is a hyperlink inthe line item. These longer footnotes may be displayed in the HTMLwindow as HTML documents.

Furthermore, as the user adds and subtracts series from a chart, thefootnotes are automatically updated from the source data, even if thereare multiple source documents. The footnotes in the RDML “Footnotes” tabalso automatically update their numbers and labels to match the chart.This is in contrast to current spreadsheet and charting programs, whichrequire that the user, not an automated lookup routine, supply thefootnotes.

The macro manager 730 manipulates and implements macros in the dataviewer 100.

Macros allow a user to apply transformations or calculations to lineitems on a one-click basis, instead of having to write formulas orqueries.

IV.A.9. Tagging Wizard

The data viewer 100 may also create XML and RDML documents 102 fromspreadsheet files. To this end, it may use a spreadsheet “wizard” tocreate tagged documents from a table of data in a spreadsheet. In oneimplementation consistent with the present invention, a wizard (using atleast one dialog box) is created in a scripting language (e.g., ExcelVisual Basic for Applications) allowing tabular data in a spreadsheet(e.g., Excel) to be used as the source for creating a tagged textdocument in the RDML format.

FIG. 21 shows a flowchart illustrating steps used in a method fortagging information from spreadsheets in accordance with the presentinvention. FIGS. 22A-D depict exemplary screen shots for differentstages in the document creation process.

FIG. 22A shows that the user makes the data ready in tabular form (step2102). Each row will become one line item; the first row 2202 willbecome the data for the “data_x” element 924. The first column 2204 willpopulate the “li-legend” attributes of the respective line items. Notethat most tabular data is already essentially in this form: the category(or time period) descriptions run across the top, the plain-languageline item descriptions run down the left, and the values themselves fillthe table.

The user then highlights the legends in the left most column 2204 andopens the first dialog box 2206 (step 2104), shown on FIG. 22B, whichwill insert new columns for information in front of the data table, eachcolumn containing one type of attribute (step 2106).

FIG. 22C shows that pressing “OK” on the dialog box 2206 creates thecolumn and fills in the default data (step 2108). The wizard inputs thedesired default values, saving most of the tedious typing, and the userchecks the columns 2208 to see if changes need to be made. Appendix Fshows exemplary code for routines that perform those functions. For eachattribute, a column is added to the spreadsheet, the correct value ofthe attribute is selected (e.g., blank, hand-worded, or taken from theappropriate field in the dialog box), and the correct number of cellsare filled with that value in the appropriate column 2208.

FIG. 22D shows that the user then brings up the document creation dialog2210 (step 2110). The user first uses the first entry field 2212 tospecify the range of the data table (including the attribute columns).The “default” data file will be used to provide defaults for therdmldoc-header element 904 values, as well as other elements andattribute values in the line_item_set element 906 (step 2112). Finally,the user fills out the remaining fields and presses “OK”, which causesthe tagged RDML document 102 to be created and saved (step 2114). Aswould be appreciated by one of ordinary skill in the art from thisdisclosure, the information gathered in the exemplary dialog boxes couldinstead be gathered in a single dialog box before creatingRDML-compliant data.

Appendix G provides code used in one implementation to create an RDMLdocument 102. Generally, the process comprises steps of: (1) openingfile and buffers for writing, (2) calling an element-creation method foreach element in the DTD 702 which can be nested within others, and (3)saving and closing the files when finished.

IV.A.10. Aspects of RMDL Markup Documents

RDML is designed to be used to describe numbers across industries anddomains. To do so, it provides a basic set of tags and a matchingvocabulary to describe six aspects of a table of numbers: (1) value, (2)structure, (3) format, (4) semantics, (5) provenance, and (6)measurement.

Value denotes that numbers are transmitted as strings, with additionaltags to define their data type, degrees of precision, handling ofmissing values, handling of nulls, and other directives to the endapplication.

Structure refers to a structuring of the data in within a table. RDMLpermits records to be arranged hierarchically within a table. Althoughnot a standard approach for relational tables, this permits multiplelevels of information to be placed in a single two-dimensional table.Users desire this, for example, when viewing financial statements, wherea single line item (e.g., “Equipment leasing”) may have severalsub-components (“Autos,” “Trucks,” “Office Equipment.”).

Format allows the application to present users with numbers in humanreadable form. The tags specify default formats for numbers,internationalization issues such as comma/decimal point handling, anddefault legends and chart titles. These formats may be changed by theusers at run time.

Semantics refers to the fact that RDML provides generic tags in whichindicators of the “meaning” of the numbers, including the vocabulariesof other SGML and XML markup languages, can be placed. This allows RDMLto act as a “wrapper” for data from other markup language documents.Semantic meaning is also conveyed in text-based attributes: legends,titles, labels, footnotes, etc.

Provenance is the documentation of various elements. RDML elementsinclude information on the source of the data, who marked it up,timestamps and link addresses, and licensing information, etc.

Finally, in the context of generic numbers, “Measurement” refers to thecharacteristics necessary to describe the measurement aspects of thedomain the number is taken from: units (“meters”, “feet”), magnitude(“millions”, “billions”), modifiers (“Adjusted for inflation, 1997index”), and so forth. This permits macros to ensure the results of anycalculation are adequately derived and described to the end user.

IV.B. Graphical User Interface and HTML Browser

The screen shots of FIGS. 14A-D, 16 and 17 have been of the graphicaluser interface (“GUI”) 734 which has several responsibilities.Generally, it creates itself and other visual components upon start-upof the application, and provides a central storage place for a minimalnumber of global variables of the application (such as file directories,etc.). Further, it responds to user actions, such as mouse clicks andkeyboard shortcuts, and repaints the screen, or portions of the screen,at appropriate moments.

The HTML browser 736 may be a third party component which displays HTMLfiles. Although this browser has been designated as an HTML browser, oneof ordinary skill in the art would appreciate from this disclosure thatother browsers (e.g., an XML browser) can likewise be used. Thiscomponent provides basic web-browsing capabilities and a way to viewhyperlinks for RDML documents 102. Additionally, it acts as a displaywindow for certain pages generated by the RDML data viewer 100 (such asRDML document source code, chart documentation, etc.)

IV.C. Reusable Macro Markup Language

FIG. 18 graphically shows elements of the RMML Document Type Definition1800. In one implementation consistent with the present invention, RMMLdocuments 104 conform to the rules provided by the DTD 1800. Inaccordance with one implementation of the present invention, an RMML DTD1800 is shown at Appendix D. Attributes and elements of the DTD 1800 mayalso be seen in the full sample RMML document 104 in Appendix E. Thesetwo Appendices D and E are useful for examining specific attributes andelements of the RMML DTD 1800.

The RMML DTD 1800 data structure is optimized to provide informationneeded in the order in which it is required, to reduce the learning onthe part of new users to RMML Macro development, and to avoidunnecessary duplication. The first line of the DTD 1800 in Appendix Dstarts with ‘<?xml encoding=“UTF-8”?>’ because XML documents start witha line that tells the client application, in this case, the RMMLInterpreter 1980 (described below) and the data viewer 100, what type ofdocument it is and the version of XML.

With further reference to FIG. 18, the DTD 1800 used to define RMMLmacro documents 104 is structured in a hierarchical tree structure ofelements. Each element may include a list of attributes (displayed inAppendix D, but not shown on FIG. 18) and/or an association with one ormore sub-elements. As with the RDML DTD described above, some attributesmay be required while others may be optional, depending on designparameters. At the highest level, the DTD 1800 has three elementsdescending from a root element, <macrodoc> 1802. The first element,<macro_header> 1804, contains the metadata for the document as a whole.The second, <macro_code> 1806 contains the source code expression to beevaluated, related variables, and instructions to the applicationregarding the graphical user interfaces for any parameters. The third,<macro_references> 1808 contains elements related to remote data (RDMLdocuments 102) or other macros (RMML documents 104).

The macro_header element 1804 is designed to match, as closely aspossible, the rdmldoc_header element of RDML documents 102. This saveslearning time for developers and end users, and allows reusable codemodules to be built for both purposes.

Nevertheless, in one implementation consistent with the presentinvention, the <macro_header> element 1804 contains several attributesthat are unique. In this implementation, there are 8 unique attributesin the <macro_header> element 1804. The first of these is “macro_type.”This attribute tells the application which general capability thisparticular macro requires within the context of that application. Theapplication uses this attribute in a factory class 1912 to create thecorrect type of macro object for internal use. Two example typesconsistent with this implementation are: (1) “TSL” (time series line, amacro that works with time series to create a new line or lines on thechart), and (2) “TSO” (time series overlay, a macro that works with timeseries to create a new overlay on the chart 716, such as graybackgrounds behind certain time periods.)

The result_type attribute tells the RDML data viewer 100 how to displaythe results of any transformation created by the macro. There are, inone implementation, five permissible values for this string: “ReplaceEach,” “Replace All,” “Replace AB,” “Add New,” “Add Annotation,” and“Add Overlay.” Replace Each removes every line on the chart 716 in theRDML data viewer 100, and replaces it with the transformed version. Forexample, if there are four series on the chart, all denominated in“miles”, and user selects a macro “to kilometers”, then every line willbe converted to kilometers, the miles lines erased, and the kilometerslines placed on the chart in their place.

Replace All is used where all current lines are being replaced by oneline. For example, if A and B are charted, a macro called “B as % of A”would replace them with a single line. Replace AB is a special case ofReplace All where there are only two lines charted. Add New adds a lineto whatever is plotted. For example, a macro called “Average” might drawa line through the existing line at the average level. Add Annotationadds a label with a pointer to a certain value on a chart (e.g., “2-3Stock Split”). Add Overlay adds a shaded area behind certain regions ofthe chart.

The attribute “rdmldoc_type” designates the type of RDML Document 102with which the macro is designed to work. Valid strings for thisattribute are TS, CT and XY, corresponding to the types of RDMLDocuments 102.

The elements <macro_source> 1810 and <license_terms> 1812 are identicalto, and play the same role as, <data_source> 908 and <license_terms> 914in the RDML Document Type Definition 702. The <documentation> 1814element is a container for two sub-elements: <macro_description> 1816and <help_page> 1818. The <macro_description> element contains a shortstring (e.g., under 50 characters) which describes the basicfunctionality of the macro. It appears in the description label of theparameters panel 1960 (shown in FIGS. 20A-D and described below) Forusers desiring a more detailed description of the macro, the <help_page>1818 element contains a text block that provides this information. Thistext block can be read by the data viewer 100 in an HTML pane as part ofthe regular help system. This text block is intended to provideinformation on all aspects of the macro that might be of interest to theuser: its use, its code, its parameters, and its inputs.

The second top-level element is <macro_code> 1806. This section containsthe actual source code and related variables. The <code> 1820 elementcontains one or more expressions which evaluate to a transformation ofcertain numbers in the RDML data viewer 100. In one implementationconsistent with this invention, the transformations apply to the chartview 716 in the RDML data viewer 102. But transformations may also beapplied to the treeview 720 or other views.

The expression(s) in this element are formulas similar to those seen inspreadsheet formulas: the expression is a series of (1) operators, (2)literals, (3) variables, (4) functions, and (5) miscellaneous expressiondelimiters. The main difference from traditional spreadsheet formulas isthat the variables may stand for either scalars or vectors, depending onthe source or the context. A sample expression follows:

A*(B+2000)−IF(A>3,12,45)

Operators are: addition (+), subtraction (−), multiplication (*),division (/), less than (<), greater than (>), or (|), and (&). Theoperators have different meanings based on the types of thesub-expressions they work on. Operating on two vectors is interpreted aselement-by-element operation on the two vectors. Thus, A*B, where A andB are vectors, is C={a1*b1, . . . an*bn}.

Literals are defined either directly in the expression (e.g., “46”), orassigned to a variable (e.g., “pi=3.14156”).

Variables can come from one of six different places in RMML. First, theycan be defined as variables directly in the RMML document 104. This isdone by creating a <variable> element and assigning it a default value.Second, variables can be associated with graphical components in theparameters panel 1960 in the RDML data viewer 102. In one implementationconsistent with this invention, there are four different types of “guicomponents.” These are listed and described below under <gui> element1824. Third, a variable can be defined from a line item elementidentical to those found in an RDML document 102. Because they areidentical, a line item can be simply cut and pasted from an RDMLdocument 102 to an RMML document 104. Fourth, a variable can be drawnfrom a remote source. In one implementation consistent with the presentinvention, that remote source can be a hyperlink to a line item in anRDML document 102. This is accomplished by using an Xpointer hyperlinkin the “href” attribute of a variable element. Fifth, a variable can bedefined as one of the series of data that is currently plotted on thechart. In one implementation in accordance with the present invention,there can be a maximum of six series on the chart; each can be accessedby using the reserved words A, B, C, D, E, and F. As would beappreciated by one of ordinary skill in the art, any number of uniquelydefinable series may be used. If the result type attribute of a macro is“Replace All”, then the expression is evaluated once for each series,with A being the series currently being transformed. Sixth, variablescan be taken from an RDML document 102 that is already loaded in theRDML data viewer 100. In this case, the expression indicates the URL anda class string that can be found in one of the li_class elements of aline item element. The expression then uses that line item as thevariable value.

Functions that are built in are provided by the interpreter 1980 in oneimplementation consistent with the present invention and are a principalmeans of extending the language. These are in the form“FUNCTION_NAME(expression)”. Functions include: IF(x,y,z); SUM(x);AVERAGE(x); COUNT(x); MIN(x); MAX(x) and so forth.

Miscellaneous delimiters are implemented by separating expressions by asemi-colon (;). This indicates that the expressions are to be evaluatedin order. Expressions can also be grouped in parentheses to tell theinterpreter 1980 how to evaluate sub-expressions.

Any string appearing in the <instructions> element 1822 will bedisplayed in the parameters panel 1960 to give the user any last minuteinstructions or suggestions. The <gui> element 1824 contains any numberof elements that describe graphical components. These graphicalcomponents will appear in the parameters panel 1960 to give the user theability to make changes to the macro's parameters. Four gui components(not shown) may be: <comp_vector>, <comp_list>, <comp_rbutton>, and<comp_ipanel>. The <comp_vector> is a vector variable, where theindividual values of the vector can be viewed in a scrolling list box. A<comp_list> element is a scrolling list; each time the user clicks on adifferent item, the value of the variable attached to that component ischanged to the value associated with that item. A <comp_rbutton> is acollection of radio buttons; each is associated with a different value.As the user clicks on different buttons, the value associated with thecomponent itself is changed, and the macro is re-run. A <comp_ipanel> isan input field that allows the user directly to input changes to themacro.

Generally, macros are not meant to run blindly on all data. First, theinterpreter 1980 checks if the macro has any “qualifiers” that must bechecked against the data. If there are any strings in the <qualifiers>element 1826 of the RMML document 104, these are checked against stringsin the <li_class> element 930 or other elements or attributes of thedata. If the data is qualified, the interpreter 1980 will proceed withrunning the macro. For example, if the <qualifiers> element 1826 of themacro specifies “li_unit==currency”, then the macro will only be run ifthe li_unit attribute of the data being operated on is a currency value.

The <error_handling> element 1828 holds error messages that can bedisplayed by the RDML data viewer 100 if there are problems of anindicated type. The <testing> element 1830 holds instructions to testingapplications regarding automated testing routines. These applicationsundertake basic unit testing such as checking for out-of-boundsproblems, missing value problems, divide-by-zero issues, etc.

The third major section of the RMML document 104, the <macro_references>element 1808 holds references to outside macros and data sets that mightbe incorporated into the macro by reference. The two sub-elements are,accordingly, the <rmmldocs> element 1832 and the <data_docs> element1834.

IV.C.1. RMML Macro Package

Generally, there are three major areas of the RMML Macro Package: theRMML document handling classes (FIG. 19A), the graphical interface (FIG.19B), and the macro interpreter (FIG. 19C). In one implementationconsistent with the present invention, this package of software classesconnects to the RDML data viewer 100 in only a few places: it gets datafrom the ChartManager 714/ChartData 715 objects, posts its graphicalcomponents through the GUI 734 object, and can access the loaded RDMLdocuments 102 in the Primary Data Store 712.

RMML Document Handling

FIG. 19A shows objects responsible for managing the process of RMMLdocument handling: loading documents, creating internal macro objectsfrom them, cataloging them and caching them, and making them ready foruse as objects. The RMMLDoc Reader 1910 locates an RMML Document 104(either locally or over the internet) passes it to an XML Parser 706(which may be a third-party component), relays error messages if any tothe RDML data viewer 100, creates an internal representation of the RMMLDocument 104 as an RMMLDoc 1906 object, and places a reference to theRMMLDoc 1906 in the RMML_Lib 1908.

The RMMLDoc 1906 can be structured in two ways: either wrapping aTXDocument object to arrive at an RMMLDoc 1906, or creating a newRMMLDoc 1906 object with the data from the TXDocument.

The RMMLDoc 1906 object contains methods for accessing individualelements and attributes of the document in a way that is easy tocomprehend in the context of the macro package. The RMML_Lib 1908 objectis a cache for loaded and active RMMLDoc objects 1906.

The RMMLDoc 1906 is a raw collection of data about a macro—its formula,its help text, etc.—and generally does not act on data sets to transformthem. The macro's capabilities first have to be used to create aninternal object (macro interface 758) that is capable of doing thecalculations. This internal macro object 758 is created by acollaboration between the MacroLibrary 1926 object (which is a cache ofthe graphic objects for the active macros) and the MacroFactory 1912(which determines which type of internal macro to create.)

There are four types of internal macros: time series (TS), category(CT), xy plot (XY) and overlay (OVERLAY). The macro_type attribute isused by the MacroFactory 1912 to create the correct type of internalmacro: Macro_TSL 1918, Macro_CT 1920, Macro_XY 1922, and Macro_OVER 1924respectively. The MacroAdapter 1916 class performs the work of themacros.

TABLE 7 MacroAdapter −mm : MacroManager −mem : Memento −rmmldoc :RMMLDoc −eval : Evaluator −mag : MacroAssumptionGroup −desc :MacroDescription −isChangedFlag : boolean −result_type : int −curr_li :int −series_label_modifier : String −series_label_type : String+createMemento( ) : void +evaluateFormula(strExpr : String, index : int): Vector +initMacro( ) : void +performTransformation(result_type : int): void +replaceVariable(strExpr : String, index : int) : String+resetMemento(mem : MacroMemento) : void +undoTransformation( ) : void+updateChartTitle( ) : void +updateLabels( ) : void +updateLegend( ) :void +updateYAxisTitle( ) void

Described below are class methods shown in Table 7 of a MacroAdapterobject 760 in accordance with one implementation consistent with thepresent invention. First, MacroAdapter( ) is the constructor thatcreates a MacroAdapter 760 object. Before a macro is run, it has achance to make a copy of the data that it is about to transform so thatundo operations can be performed. The createMemento( ) method takes asnapshot of the data plotted on the chart by copying the ChartDataobject 715 to a Memento object.

Also, before a macro is run, the method initMacro( ) is run and givesthe macro a chance to load any remote data or macro code. ThereplaceVariable( ) method runs the macro on multiple series on a chart.For example, if the result_type is “Replace Each” and there are fourseries charted on the chart, the macro will be run four times. The firsttime, A in the formula represents the first series, the second time itrepresents the second series and so forth. The methodperformTransformation( ) evaluates the transformation string, andupdates the various titles and legends. An important part ofperformTransformation( )'s code is to determine the result_type of themacro and call the evaluateFormula( ) method in the correct manner. For“Replace Each,” it is called once for each series, while for “ReplaceAll,” it is run only once.

The performTransformation( )method also calls the four update methods:updateChartTitle( ) updateLabels( ), updateLegend( ) andupdateYAxisTitle( ). Each of these modifies the relevant strings in theChartData object 715 so it can be passed on to the chart.

RMML Graphical Interface

FIG. 19B illustrates objects responsible for managing the process ofcreating, managing, and handling events from the graphical userinterface 734. FIG. 20A shows a screen shot of the RDML data viewer 100;the NewMacroPanel 732 is displayed in the lower half of the screen. Theavailable macros are displayed in individual windows in the MacroLibrarypanel 1926 on the left side of the lower panel. The right side of themacro panel 732 is the macro information panel 2002 which holds themacro description panel 1958 and the parameter panel 1960.

The NewMacroPanel 732 may be a subclass of a JPanel 1942 in Java's Swingset of classes. Those skilled in the art will be able to chose theappropriate class to use for other major platforms. The left side of theNewMacroPanel 732 is a frame for a multiple document interface (in thiscase, a Desktop for JinternalFrame objects from Java's Swing Set). EachMacroLibrary 1926 that is opened created a new internal frame, whichallows users to select macros from multiple libraries at the same time.

When a MacroLibrary 1926 is opened, all macros within it are loaded andregistered. “Registration” is a series of methods wherein the macro'svariables are found in various elements of the RMMLDoc 104, andgraphical representations of these variables are built for inclusion inthe parameter panel 1960.

The graphical components for all of the variables associated with a setof macros are created in the MacroAssumptionGroup 1944 class. This classhas a factory method that examines the attributes of the variablesreported by the RMMLDoc 104 (variable name, variable value, gui type,default value, etc.) and creates the appropriate MacroGUl class:MacroGUl_List 1952 (see FIG. 20A), MacroGUl_RadioButton 1954 (see FIG.20B), MacroGUl_Vector 1956 (see FIG. 20C), or MacroGUl_Default 1950 (seeFIG. 20D). Each of these graphical components appears differently in theparameter panel 1960 as shown in the screen shots noted.

The registration of macros by the MacroLibrary 1926 also involvescreating an MVariable 1946 object to go with each variable, and addingthese to a cache of available Mvariables 1946. These Mvariable 1946objects are used in the actual evaluation of expressions. Theregistration process also involves registering the MacroGUl 1948 objectsas sources for events that the MacroManager 1980 object can use totrigger the running of a macro. Mvariables 1946 encapsulate the variouscharacteristics of a variable: its value, default, and source.

The description panel 1958 and the parameter panel 1960 are populatedwith graphical components and text when a particular macro is selectedin the treeview 720 listing of a MacroLibrary 1926 internal frame. Themacro that is selected provides the description text, the various labelsand the MacroGUl 1948 components.

RMML Interpreter

The MacroManager object 730 is responsible for detecting that a macrohas been selected or a parameter changed, getting the various data setsand variables called up and made available to an Evaluator object 1984,and that the data set charted (or showing on the treeview 720) isobtained and transformed and sent back to be recharted on the chart 716or relisted on the treeview.

ChartData 715 contains the data from the current chart 716 (or activetreeview 720, depending on the type of the macro). It makes this dataavailable as just another variable to the Evaluator object 1984, andtakes the final result of the Evaluator object 1984.

The Evaluator 1984 evaluates the string expression(s) in the <code>element 1920 of the RMML document 104, or the various expressions fromthe macros that have been selected. The expression is broken up intotokens by the Tokenizer classes 1994. These tokens are the variousoperators, variables, literals, functions and other control symbols usedin the RMML expression language detailed above. From these tokens, theFormula object 1990 builds a parse tree, by recursive descent, made upof FormulaNode 1992 objects created from the tokens. The FormulaNode1992 objects evaluate themselves using the resolver objectsVariableResolver 1986 and FunctionResolver 1988. These resolvers in turncall the Evaluator objects 1984 to give them the current value of avariable or a function. For example, the FormulaNode 1982 evaluationprocess may have an “A” token; the Evaluator object 1984 knows that thismeans series A on the chart, and uses the vector of data (it could be anarray or other data structure) currently found in the chart 716. Theformula exception 1996 relays errors associated with the processing of afunction.

The foregoing description of an implementation of the present inventionhas been presented for purposes of illustration and description. It isnot exhaustive and does not limit the present invention to the preciseform disclosed. Modifications and variations are possible in light ofthe above teaching or may be acquired from practicing of the presentinvention. The scope of the present invention is defined by the claimsand their equivalents.

APPENDIX A RDML Document Type Definition (“DTD”) <?xmlencoding=“UTF-8”?> <!-- The root element: a whole portfolio of data isan “rdmldoc” --> <!ELEMENT rdmldoc (rdmldoc_header, line_item_set)> <!--RDMLDOC_HEADER --> <!-- Information about the rdmldoc. An rdmldocconsists of an  rdmldoc_header and a line_item_set. Line items in the line_item_set share a common data structure. --> <!ELEMENTrdmldoc_header (data_source?, formatting_source?, rdmldoc_source?,license_terms?, linkset?)> <!ATTLIST rdmldoc_header rdmldoc_ID CDATA#REQUIRED doc_title CDATA #REQUIRED timestamp CDATA #REQUIRED versionCDATA #IMPLIED expiration CDATA #IMPLIED freq_of_update CDATA #IMPLIEDnum_line_items CDATA #IMPLIED num_datapoints CDATA #IMPLIED x_indexesCDATA #IMPLIED first_li_withdata CDATA #IMPLIED > <!ELEMENT data_source(contact_info+)> <!ELEMENT formatting_source (contact_info+)> <!ELEMENTrdmldoc_source (contact_info+)> <!ELEMENT license_terms (contact_info?,linkset?)> <!ATTLIST license_terms copyright_cite CDATA #REQUIRED holderCDATA #REQUIRED license_type CDATA #IMPLIED warranty CDATA #IMPLIEDdisclaimer CDATA #IMPLIED terms CDATA #IMPLIED date CDATA #IMPLIED emailCDATA #IMPLIED state CDATA #IMPLIED country CDATA #IMPLIED > <!ELEMENTcontact_info (#PCDATA)> <!ATTLIST contact_info role CDATA #REQUIRED nameCDATA #IMPLIED company CDATA #IMPLIED address CDATA #IMPLIED city CDATA#IMPLIED state CDATA #IMPLIED zip CDATA #IMPLIED country CDATA #IMPLIEDemail CDATA #IMPLIED form CDATA #IMPLIED href CDATA #IMPLIED commentsCDATA #IMPLIED > <!ELEMENT linkset (link*)> <!ATTLIST linkset form CDATA#FIXED ‘extended’ href CDATA #IMPLIED > <!ELEMENT link (#PCDATA) ><!ATTLIST link form CDATA #FIXED ‘simple’ href CDATA #REQUIRED behaviorCDATA #IMPLIED content-role CDATA #IMPLIED content-title CDATA #IMPLIEDrole CDATA #IMPLIED title CDATA #IMPLIED show CDATA #FIXED ‘new’ actuateCDATA #FIXED ‘user’ > <!-- LINE_ITEM_SET --> <!-- Information about thecollection of line items --> <!ELEMENT line_item_set (data_x,li_class_set?, linkset?, line_item+) > <!ATTLIST line_item_setline_item_set_type CDATA #REQUIRED time_period CDATA #REQUIREDcharacter_set CDATA #IMPLIED missing_values CDATA #IMPLIED null_valuesCDATA #IMPLIED zero_values CDATA #IMPLIED dates_values CDATA #IMPLIEDpercentages CDATA #IMPLIED > <!ELEMENT data_x (#PCDATA) > <!ATTLISTdata_x x_title CDATA #REQUIRED format CDATA #REQUIRED x_notes CDATA#IMPLIED x_desc CDATA #IMPLIED x_prec CDATA #REQUIRED x_unit CDATA#REQUIRED x_mag CDATA #REQUIRED x_mod CDATA #REQUIRED x_measure CDATA#REQUIRED x_scale CDATA #REQUIRED x_adjustment CDATA #REQUIRED x_linksCDATA #REQUIRED > <!ELEMENT li_class_set (li_class+)> <!ELEMENT li_class(#PCDATA)> <!ATTLIST li_class class_name CDATA #REQUIRED parent_classCDATA #REQUIRED form CDATA #FIXED ‘simple’ href CDATA #IMPLIEDdescription CDATA #IMPLIED > <!-- LINE_ITEM --> <!-- Information aboutthe Line Item --> <!ELEMENT line_item (data_x?, data_y, linkset?,note_set?) > <!ATTLIST line_item li_ID CDATA #REQUIRED li_legend CDATA#REQUIRED li_title CDATA #REQUIRED li_cat CDATA #IMPLIED y_axis_titleCDATA #REQUIRED level CDATA #REQUIRED format CDATA #REQUIRED relationCDATA #REQUIRED li_notes CDATA #REQUIRED li_desc CDATA #REQUIRED li_precCDATA #REQUIRED li_unit CDATA #REQUIRED li_mag CDATA #REQUIRED li_modCDATA #REQUIRED li_measure CDATA #REQUIRED li_scale CDATA #REQUIREDli_adjustment CDATA #REQUIRED li_aggregation CDATA #IMPLIED > <!ELEMENTdata_y (#PCDATA)> <!ELEMENT analysis (linkset?)> <!ELEMENT note_set(note+)> <!ELEMENT note (#PCDATA)> <!ATTLIST note note_type CDATA#IMPLIED >

APPENDIX C UnitList XML document <?xml version=“1.0” encoding=“utf-8” ?><unitlist> <unit name=“inch”>  <conversion   conv_target = “centimeter”  conv_factor = “2.5400050”   conv_constant = “”   conv_log = “”  conv_source = “FGM”   conv_href = “”>  </conversion> <type>Length</type>  <subtype>Linear</subtype>  <plural>inches</plural> <alias>in</alias>  <desc>Approximately the width of a man'sthumb.</desc>  <icon href=“inch.gif”></icon> </unit> <unit name=“foot”> <conversion   conv_target = “meter”   conv_factor = “0.30480060”  conv_constant = “”   conv_log = “”   conv_source = “ISO”   conv_href =“”>  </conversion>  <type>length</type>  <subtype>Linear</subtype> <plural>feet</plural>  <alias>ft</alias>  <desc>Originally, the averagelength of a human foot</desc>  <icon href=“foot.gif”></icon> </unit><unit name=“yard”>  <conversion   conv_target = “meter”   conv_factor =“1.082”   conv_constant = “”   conv_log = “”   conv_source = “ISO”  conv_href = “”>  </conversion>  <type>length</type> <subtype>Linear</subtype>  <plural>yards</plural>  <alias></alias> <desc>Three feet</desc>  <icon href=“yard.gif”></icon> </unit> <unitname=“meter”>  <conversion   conv_target = “meter”   conv_factor = “1.0”  conv_constant = “”   conv_log = “”   conv_source = “ISO”   conv_href =“”>  </conversion>  <type>length</type>  <subtype>Linear</subtype> <plural>meters</plural>  <alias>m,mtr</alias>  <desc>One thousandth ofa kilometer</desc>  <icon href=“meter.gif”></icon> </unit> <unitname=“mile”>  <conversion   conv_target = “kilometer”   conv_factor =“1.6093472”   conv_constant = “”   conv_log = “”   conv_source = “FGM”  conv_href = “”>  </conversion>  <type>length</type> <subtype>Linear</subtype>  <plural>miles</plural>  <alias></alias> <desc>English surveying unit, set to be equal to 8 furlongs.</desc> <icon href=“mile.gif”></icon> </unit> <unit name=“dollar”>  <conversion  conv_target = “pound”   conv_factor = “1.312”   conv_constant = “”  conv_log = “”   conv_source = “ISO”   conv_href = “”>  </conversion> <type>currency</type>  <plural>pounds</plural>  <alias>sterling</alias> <desc>British pound sterling. </desc>  <icon href=“pound.gif”></icon></unit> <unit name=“Deutschmark”>  <conversion   conv_target = “dollar”  conv_factor = “1.732”   conv_constant = “”   conv_log = “”  conv_source = “ISO”   conv_href = “”>  </conversion> <type>currency</type>  <plural>Duetschmarkse</plural> <alias>Marks</alias>  <desc>German Deutschmarks</desc>  <iconhref=“marks.gif”></icon> </unit> <unit name=“Francs”>  <conversion  conv_target = “dollar”   conv_factor = “0.812”   conv_constant = “”  conv_log = “”   conv_source = “ISO”   conv_href = “”>  </conversion> <type>currency</type>  <plural>francs</plural>  <alias>ff</alias> <desc>French francs</desc>  <icon href=“francs.gif”></icon> </unit><unit name=“acres”>  <conversion   conv_target = “square meter”  conv_factor = “5125”   conv_constant = “”   conv_log = “”  conv_source = “ISO”   conv_href = “”>  </conversion> <type>area</type>  <plural>acres</plural>  <alias>acr</alias>  <desc>Inmedieval times, the amount of land one man  could plow in oneday.</desc>  <icon href=“acre.gir></icon> </unit> <unit name=“squarefoot”>  <conversion   conv_target = “square meter”   conv_factor =“0.15”   conv_constant = “”   conv_log = “”   conv_source = “ISO”  conv_href = “”>  </conversion>  <type>area</type>  <plural>squarefeet</plural>  <alias>sq ft</alias>  <desc>An area one foot by onefoot.</desc>  <icon href=“sqfoot.gif”></icon> </unit> </unitlist>

APPENDIX D RMML Document Type Definition (“DTD”) <?xmlencoding=“UTF-8”?> <!-- The root element: a whole macro is a “macrodoc”.A macrodoc consists of three elements:  a macro_header, a macro_code,and a macro_references element. --> <!ELEMENT macrodoc (macro_header,macro_code, macro_references)> <!-- MACRO_HEADER --> <!-- Informationabout the macro. --> <!ELEMENT macro_header (macro_source,license_terms, linkset?, documentation)> <!ATTLIST macro_header   macrodoc_ID CDATA #REQUIRED    macro_title CDATA #REQUIRED   macro_type CDATA #REQUIRED    result_type CDATA #REQUIRED   rdmldoc_type CDATA #REQUIRED    timestamp CDATA #IMPLIED    versionCDATA #IMPLIED    expiration CDATA #IMPLIED    freq_of_update CDATA#IMPLIED > <!ELEMENT macro_source (contact_info+)> <!ELEMENTlicense_terms (contact_info, linkset?)> <!ATTLIST license_terms   copyright_cite CDATA #REQUIRED    holder CDATA #IMPLIED   license_type CDATA #IMPLIED    warranty CDATA #IMPLIED    disclaimerCDATA #IMPLIED    terms CDATA #IMPLIED    date CDATA #IMPLIED    emailCDATA #IMPLIED    state CDATA #IMPLIED    country CDATA #IMPLIED ><!ELEMENT contact_info (#PCDATA)> <!ATTLIST contact_info    role CDATA#IMPLIED    name CDATA #IMPLIED    company CDATA #IMPLIED    addressCDATA #IMPLIED    city CDATA #IMPLIED    state CDATA #IMPLIED    zipCDATA #IMPLIED    country CDATA #IMPLIED    email CDATA #IMPLIED   xlink:form CDATA #IMPLIED    href CDATA #IMPLIED    comments CDATA#IMPLIED > <!ELEMENT linkset (link*)> <!ATTLIST linkset    xlink_formCDATA #FIXED ‘extended’    href CDATA #IMPLIED > <!ELEMENT link(#PCDATA) > <!ATTLIST link    xlink_form CDATA #FIXED ‘simple’    hrefCDATA #REQUIRED    behavior CDATA #IMPLIED    content-role CDATA#IMPLIED    content-title CDATA #IMPLIED    role CDATA #IMPLIED    titleCDATA #IMPLIED    show CDATA #FIXED ‘new’    actuate CDATA #FIXED‘user’> <!ELEMENT documentation (macro_description, help_page*)><!ELEMENT macro_description (#PCDATA)> <!ELEMENT help_page (#PCDATA)><!ELEMENT macro_code (code, instructions, gui, variable_set?,qualifiers, error_handling, testing)> <!ELEMENT code (#PCDATA)><!ELEMENT instructions (#PCDATA)> <!ELEMENT gui (comp_rpanel? |comp_ipanel? | comp_list? | comp_vector?)> <!ELEMENT comp_rpanel(comp_rbutton*)> <!ATTLIST comp_rpanel    variable_name CDATA #REQUIRED   intro_label CDATA  #IMPLIED    visible CDATA #IMPLIED    legend CDATA#IMPLIED    legend_type CDATA #IMPLIED > <!ELEMENT comp_rbutton(#PCDATA)> <!ATTLIST comp_rbutton    Label CDATA #REQUIRED    valueCDATA #REQUIRED    isDefault CDATA #REQUIRED    icon CDATA #IMPLIED   desc CDATA #IMPLIED    legend CDATA #IMPLIED    legend_type CDATA#IMPLIED > <!ELEMENT comp_ipanel (comp_ifield*)> <!ELEMENT comp_ifield(#PCDATA)> <!ATTLIST comp_ifield    variable_name CDATA #REQUIRED   variable_label CDATA #REQUIRED    intro_label CDATA #REQUIRED   default_value CDATA #REQUIRED    desc CDATA #IMPLIED    legend CDATA#IMPLIED    legend_type CDATA #IMPLIED > <!ELEMENT comp_list(comp_listitem*)> <!ATTLIST comp_list    variable_name CDATA #REQUIRED   intro_label CDATA #REQUIRED    default_item CDATA #REQUIRED    legendCDATA #IMPLIED    legend_type CDATA #IMPLIED > <!ELEMENT comp_listitem(#PCDATA)> <!ATTLIST comp_listitem    label CDATA #REQUIRED    valueCDATA #REQUIRED    icon CDATA #IMPLIED    desc CDATA #IMPLIED    legendCDATA #IMPLIED    legend_type CDATA #IMPLIED > <!ELEMENT comp_vector(line_item)> <!ATTLIST comp_vector    variable_name CDATA #REQUIRED   intro_label CDATA #REQUIRED    default_item CDATA #REQUIRED    descCDATA #IMPLIED    legend CDATA #IMPLIED    legend_type CDATA #IMPLIED ><!ELEMENT variable_set (variable*)> <!ELEMENT variable (#PCDATA |line_item)*> <!ATTLIST variable    variable_name CDATA #REQUIRED   variable_type CDATA #REQUIRED    value CDATA #REQUIRED    href CDATA#IMPLIED    subref CDATA #IMPLIED > <!ELEMENT qualifiers (#PCDATA)><!ELEMENT error_handling (#PCDATA)> <!ELEMENT testing (#PCDATA)><!ELEMENT macro_references (macrodocs?, datadocs?)> <!ELEMENT macrodocs(#PCDATA)> <!ELEMENT datadocs (#PCDATA)> <!ELEMENT line_item (data_x?,data_y, linkset?, note_set?) > <!ATTLIST line_item    li_ID CDATA#REQUIRED    li_legend CDATA #REQUIRED    li_title CDATA #REQUIRED   li_cat CDATA #IMPLIED    y_axis_title CDATA #REQUIRED    level CDATA#REQUIRED    format CDATA #REQUIRED    relation CDATA #REQUIRED   li_notes CDATA #REQUIRED    li_desc CDATA #REQUIRED    li_prec CDATA#REQUIRED    li_unit CDATA #REQUIRED    li_mag CDATA #REQUIRED    li_modCDATA #REQUIRED    li_measure CDATA #REQUIRED    li_scale CDATA#REQUIRED    li_adjustment CDATA #REQUIRED    li_aggregation CDATA#IMPLIED > <!ELEMENT data_y (#PCDATA)> <!ELEMENT note_set (note+)><!ELEMENT note (#PCDATA)> <!ATTLIST note    note_type CDATA #IMPLIED ><!ELEMENT data_x (#PCDATA) > <!ATTLIST data_x    x_title CDATA #REQUIRED   format CDATA #REQUIRED    x_notes CDATA #IMPLIED    x_desc CDATA#IMPLIED    x_prec CDATA #REQUIRED    x_unit CDATA #REQUIRED    x_magCDATA #REQUIRED    x_mod CDATA #REQUIRED    x_measure CDATA #REQUIRED   x_scale CDATA #REQUIRED    x_adjustment CDATA #REQUIRED    x_linksCDATA #REQUIRED >

APPENDIX E Sample RMML document <?xml version=“1.0” encoding=“UTF-8”standalone=“no”?> <!DOCTYPE macrodoc PUBLIC “-//..” “RMML1.dtd” ><macrodoc>   <macro_header   macrodoc_ID = “rmml_sort”   macro_title =“Sort”   macro_type = “TSL”   result_type = “replace_each”  rdmldoc_type = “TS”   timestamp = “1999-01-19T23:00:00”   version =“1.0.0”   expiration = “2000-01-19T23:00:00”   freq_of update =“Annual” > <macro_source>   <contact_info   role = “Macro Source”   name= “Russell T. Davis”   company = “RDML, Inc.”   address = “2 WisconsinCircle, Suite 700”   city = “Chevy Chase”   state = “MD”   zip = “20815”  country = “USA”   email = “rt_davis@sprynet.com”   href =“http://www.rdml.com”   comments = “” >   </contact_info></macro_source> <license_terms   copyright_cite = “Copyright 1998, RDML,Inc. All Rights Reserved”   holder = “RDML, Inc.”   license_type =“Payment Per Download”   warranty = “No warranty is expressed orimplied. Use this data at your   own risk.”   disclaimer = “This data isprovided ‘as-is’. The provider assumes no responsibility for its use ormisuse.”   terms = “$1 per RMMLDoc download”   date =“1999.0123000000.00”   email = “license@rdml.com”   state = “MD”  country = “USA” >   <contact_info   role = “Licensee”   name =“Russell T. Davis”   company = “RDML, Inc.”   address = “2 WisconsinCircle, Suite 700”   city = “Chevy Chase”   state = “MD”   zip = “20815”  country = “USA”   email = “rt_davis@sprynet.com”   href =“http://www.rdml.com”   comments = “” >   </contact_info></license_terms> <linkset   xlink_form = “extended”   href =“http://www.rdnd.com” >   <link   xlink_form = “simple”   href =“http://www.rdml.com”   behavior = “”   content-role = “”  content-title = “”   role = “”   title = “”   show = “new”   actuate =“user” >   </link> </linkset> <documentation>   <macro_description> Addsa line showing the minimum or maximum, according to the parameters  </macro_description>   <help_page>   No Help Page is currentlyavailable   </help_page> </documentation> </macro_header> <macro_code>  <code>   IF(ichoice=0, SORT(A,0), 1F(ichoice=1, SORT(A,1), A)) </code><instructions> </instructions> <gui>   <comp_rpanel    variable_name =“ichoice”    intro_label = “Select a parameter:” >    <comp_rbutton   label = “Ascending”    value = “0”    isDefault = “true”    icon =“” >    </comp_rbutton>    <comp_rbutton    label = “Descending”   value = “1”    isDefault = “false”    icon = “” >    </comp_rbutton>  </comp_rpanel>   </gui>   <qualifiers>   </qualifiers>  <error_handling>   </error_handling>   <testing>   </testing></macro_code>   <macro_references>   <macrodocs>   </macrodocs>  <datadocs>   </datadocs>  </macro_references> </macrodoc>

APPENDIX F MS Excel Visual Basic routine for adding “attribute valuecolumns” to a data table Private Sub UserForm Initialize( ) cmdOK.SetFocus  txtChartTitle.Text = “”  txtYAxisTitle.Text = “” cboFormat.AddItem (“#,##00;(#,##0)”)  cboFormat.AddItem(“#,##0.00;(#,##0.00)”)  cboFormat.AddItem (“0.00%;(0.00%)”) cboFormat.ListIndex = 0  txtFootnote.Text = “Source: ”  Dim NodeX AsNode  Set NodeR = treeUnit.Nodes.Add(, , “r”, “Select One: (Default is blank)”)  ′Currency  Set NodeA = treeUnit.Nodes.Add(“r”, tvwChild, “c”,“Currency”)  Set Nodes = treeUnit.Nodes.Add(“c”, tvwChild, “dus”, “$US”)  Set NodeX = treeUnit.Nodes.Add(“c”, tvwChild, “puk”, “Pounds UK”) Set NodeX = treeUnit.Nodes.Add(“c”, tvwChild, “yjp”, “Yen  Japanese”) ′Length  Set NodeX = treeUnit.Nodes.Add(“r”, tvwChild, “1”, “Length”) Set NodeX = treeUnit.Nodes.Add(“1”, tvwChild, “Feet”, “Feet”)  SetNodeX = treeUnit.Nodes.Add(“1”, tvwChild, “Meters”, “Meters”)  ′Area Set NodeX = treeUnit.Nodes.Add(“r”, tvwChild, “a”, “Area”)  Set NodeX =treeUnit.Nodes.Add(“a”, tvwChild, “SqFeet”,  “Square Feet”)  Set NodeX =treeUnit.Nodes.Add(“a”, tvwChild, “SqMeters”,  “Square Meters”)  ′treeformatting  NodeA.EnsureVisible  ′Magnitude ComboBox cboMagnitude.AddItem (“As-Is”)  cboMagnitude.AddItem (“Thousands”) cboMagnitude.AddItem (“Millions”)  cboMagnitude.AddItem (“Billions”) cboMagnitude.Listlndex = 0 End Sub Private Sub cmdCancel_Click( )  EndEnd Sub Private Sub cmdOK_Click( )  rcount = Selection.Rows.Count ′li_ID  Selection.EntireColumn.Insert  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_ID”  ActiveCell.Offset(1,0).Range(“A1”).Select  ActiveCell.FormulaR1C1 = “1” ActiveCell.Offset(1, 0).Range(“A1”).Select  ActiveCell.FormulaR1C1 =“=R[−1]C+1”  ActiveCell.Select  Selection.Copy  r = “A1:A” & (rcount −3)  ActiveCell.Offset(1, 0).Range(r).Select  ActiveSheet.Paste Application.CutCopyMode = False  ′li_legend  ActiveCell.Offset(−3, 1).Range(“A1”).Select  ActiveCell.FormulaR1C1 = “li_legend”  ′li_title ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_title”  ActiveCell.Offset(1,0).Range(“Al”).Select  ActiveCell.FormulaR1C1 = txtChartTitle.Text ActiveCell.Select  Selection.Copy  r = “A1:A” & (rcount − 2) ActiveCell.Offset(1, 0).Range(r).Select  ActiveSheet.Paste Application.CutCopyMode = False  ′li_cat  ActiveCell.Offset(0,1).Columns(“A:A”).EntireColumn.Select  Selection.Insert Shift:=xlToRight ActiveCell.Select  ActiveCell.FormulaR1C1 = “li_cat”  ′y_axis_title ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “y_axis_title”  ActiveCell.Offset(1,0).Range(“A1”).Select  ActiveCell.FormulaR1C1 = txtYAxisTitle.Text ActiveCell.Select  Selection.Copy  r = “A1:A” & (rcount − 2) Selection.ColumnWidth = 8  ActiveCell.Offset(1, 0).Range(r).Select ActiveSheet.Paste  Application.CutCopyMode = False  ′level ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “level”  ActiveCell.Offset(1,0).Range(“A1”).Select  ActiveCell.FormulaR1C1 = “1”  ActiveCell.Select Selection.Copy  r = “A1:A” & (rcount − 2)  Selection.ColumnWidth = 8 ActiveCell.Offset(1, 0).Range(r).Select  ActiveSheet.Paste Application.CutCopyMode = False  ′format  ActiveCell.Offset(0,1).Columns(“A:A”).EntireColumn.Select  Selection.Insert Shift:=xlToRight ActiveCell.Select  ActiveCell.FormulaR1C1 = “format” ActiveCell.Offset(1, 0).Range(“A1”).Select  ActiveCell.FormulaR1C1 =cboFormat.value  ActiveCell.Select  Selection.Copy  r = “A1:A” & (rcount− 2)  ActiveCell.Offset(1, 0).Range(r).Select  ActiveSheet.Paste Application.CutCopyMode = False  ′relation  ActiveCell.Offset(0,1).Columns(“A:A”).EntireColumn.Select  Selection.Insert Shift:=xlToRight ActiveCell.Select  ActiveCell.FormulaR1C1 = “relation” ActiveCell.Offset(1, 0).Range(“A1”).Select  ActiveCell.FormulaR1C1 =“Parent”  ActiveCell.Select  Selection.Copy  r = “A1:A” & (rcount − 2) ActiveCell.Offset(1, 0).Range(r).Select  ActiveSheet.Paste Application.CutCopyMode = False  ′li_notes  ActiveCell.Offset(0,1).Columns(“A:A”).EntireColumn.Select  Selection.Insert Shift:=xlToRight ActiveCell.Select  ActiveCell.FormulaR1C1 = “li_notes” ActiveCell.Offset(1, 0).Range(“A1”).Select  ActiveCell.FormulaR1C1 =txtFootnote.Text  ActiveCell.Select  Selection.Copy  r = “A1:A” &(rcount − 2)  Selection.ColumnWidth = 8  ActiveCell.Offset(1,0).Range(r).Select  ActiveSheet.Paste  Application.CutCopyMode = False ′li_desc  ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_desc”  ′li_prec  ActiveCell.Offset(0,1).Columns(“A:A”).EntireColumn.Select  Selection.Insert Shift:=xlToRight ActiveCell.Select  ActiveCell.FormulaR1C1 = “li_prec”  ′li_unit ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_unit”  ActiveCell.Offset(1,0).Range(“A1”).Select  u = “”  On Error Resume Next  u =treeUnit.SelectedItem.Text  ActiveCell.FormulaR1C1 = u ActiveCell.Select  Selection.Copy  r = “A1:A” & (rcount − 2) ActiveCell.Offset(1, 0).Range(r).Select  ActiveSheet.Paste Application.CutCopyMode = False  ′li_mag  ′first calculate the value toput in  If (StrComp(cboMagnitude.value, “As-Is”) = 0) Then   m = 0  EndIf  If (StrComp(cboMagnitude.value, “Thousands”) = 0) Then   m = 3  EndIf  If (StrComp(cboMagnitude.value, “Millions”) = 0) Then   m = 6  EndIf  If (StrComp(cboMagnitude.value, “Billions”) = 0) Then   m = 9  EndIf  ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_mag”  ActiveCell.Offset(1,0).Range(“A1”).Select  ActiveCell.FormulaR1C1 = m  ActiveCell.Select Selection.Copy  r = “A1:A” & (rcount − 2)  ActiveCell.Offset(1,0).Range(r).Select  ActiveSheet.Paste  Application.CutCopyMode = False ′li_mod  ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_mod”  ′li_measure  ActiveCell.Offset(0,1).Columns(“A:A”).EntireColumn.Select  Selection.Insert Shift:=xlToRight ActiveCell.Select  ActiveCell.FormulaR1C1 = “li_measure”  ′li_scale ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_scale”  ′li_adjustment ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift:=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_adjustment”  ′li_aggregation ActiveCell.Offset(0, 1).Columns(“A:A”).EntireColumn.Select Selection.Insert Shift=xlToRight  ActiveCell.Select ActiveCell.FormulaR1C1 = “li_aggregation”  End End Sub

APPENDIX G MS Excel Visual Basic routine creating a tagged document froma spreadsheet data table Private Sub Framel_Click( ) End Sub Private SubUserForm_Initialize( )  cmdOK.SetFocus  RefEdit_data.value =“Sheet1!$A$1:$AB$51”  txtDefaultFile.Text = “DAdefault1.rdm” txtOutputDir.Text = “D:\”  txtOutputFile.Text = “out.rdm” cboLineItemType.AddItem (“TimeSeries”)  cboLineltemType.Addltem(“Category”)  cboLineltemType.Addltem (“XYPlot”) cboLineltemType.Listlndex = 0  cbNonFileDefaults.value = False End SubPrivate Sub cmdCancel_Click( )  End End Sub Private Sub cmdOK_Click( ) Dim buff As String  buff = createIntro  buff = buff & createHeader buff = buff & createLlSet  buff = buff & createLineltems  buff = buff &“</line_item_set>” & Chr(10)  buff = buff & createEnding replaceAttribute buff, “rdmldoc_header”, “rdmldoc_ID”,txtOutputFile.value  replaceAttribute buff, “rdmldoc_header”,“doc_title”, txtDocTitle.value  replaceAttribute buff, “line_item_set”,“line_item_set_type”, cboLineItemType.SelText    replaceAttribute buff,“data_x”, “x_title”, txtXAxisTitle.value    fillXData buff    CreateFile(buff)    End   End Sub   Private Sub cmdBrowseDefault_Click( )   CommonDialog1.ShowOpen    txtDefaultFile.Text =ComrnonDialog1.Filename   End Sub   Private SubcmdBrowseOutputDir_Click( )    CorrimonDialog1.ShowOpen   txtOutputFile.Text = CommonDialog1.Filename   End Sub   Private SubUserForm_Click( )   End Sub   Private Sub getConfiguration( )   End Sub  Private Function createHeader( )    ′buff will be the buffer thatcollects the string    Dim buff As String    ′If user wants the programto create a default    If cbNonFileDefaults.value = True Then     buff =buff & defHeader    End If    ′Or get the default header values from afile    buff = createDefHeader    ′return    createHeader = buff   EndFunction   Private Function createDefHeader( )  ′Declarations  Dim h AsString  Dim wholefile As String  ′open the default file  Dim Def_file AsString  Def_file = txtDefaultFile.Text  Open Def_file For Input As #2 wholefile = Input$(LOF(2), 2)  Close #2  ′put the rdmldoc_header into astring  h = getElementByTagName(wholefile, “rdmldoc_header”) createDefHeader = h End Function Private Function createLISet( ) ′Declarations  Dim h As String  Dim wholefile As String  ′open thedefault file  Dim Def_file As String  Def_file = txtDefaultFile.Text Open Def_file For Input As #2  wholefile = Input$(LOF(2), 2)  Close #2 ′put the the line item set overall tags into a string  h =getOpeningElementTag(wholefile, “line_item_set”)  h = h &getElementByTagName(wholefile, “data_x”)  h = h &getElementByTagName(wholefile, “li_class_set”)  h = h &getElementByTagName(wholefile, “linkset”)  createLISet = h End FunctionPublic Function getElementByTagName(str As String, el As String) startPos = InStr(1, str, “<” & el, 1)  endPos = InStr(1, str, “</” &el, 1)  element = Mid(str, startPos, endPos − startPos + Len(el) + 4) getElementByTagName = element End Function Public FunctiongetOpeningElementTag(str As String, el As String)  startPos = InStr(1,str, “<” & el, 1)  endPos = InStr(startPos, str, “>”, 1)  element =Mid(str, startPos, endPos − startPos + 5)  getOpeningElementTag =element End Function Private Sub CreateFile(buff)  Dim Outfile As String Outfile = txtOutputDir.Text & txtOutputFile.Text  Open Outfile ForOutput As #1  Print #1, buff  Close #1 End Sub Private FunctioncreateIntro( )  buff = “”  ′Header Information  buff = buff & “<?xmlversion=” & Chr(34) & “1.0” & Chr(34)  buff = buff & “encoding=” &Chr(34) & “UTF-8” & Chr(34)  buff = buff & “standalone=” & Chr(34) &“no” & Chr(34)  buff = buff & “?>” & Chr(10)  ′DTD Declaration  buff =buff & “<!DOCTYPE rdmldoc PUBLIC”  buff = buff & Chr(34) & “-//..” &Chr(34) & “”  buff = buff & Chr(34) & “RDML1.dtd” & Chr(34)  buff = buff& “>” & Chr(10)  ′begin rdmldoc tag  buff = buff & “<rdmldoc>” & Chr(10) ′return  createIntro = buff End Function Private Function createEnding()  buff = “”  buff = buff & “</rdmldoc>” & Chr(10)  ′return createEnding = buff End Function Private Function defHeader( )  buff =“”  ′return  defHeader = buff End Function Private FunctioncreateLineItems( )  Dim data As Range  t = RefEdit_data.value createLineItems = fillLineItems(Range(t), cboLineItemType.value) EndFunction′---------------------------------------------------------------------------------------′ Procedure: Fill_line_item( ) ′ Purpose: Prepare the line_item element′ This element contains information about the line_item ′ From DTD:′<!ELEMENT line_item (data_x?, data_y, li_class_set?, analysis?,′link_set?, note_set?)> ′<!ATTLIST line_item ′ li_ID CDATA   #REQUIRED ′li_legend CDATA   #REQUIRED ′ li_title CDATA   #REQUIRED ′ li_tableCDATA   #IMPLIED ′ y_axis_title CDATA   #REQUIRED ′ level CDATA  #REQUIRED ′ format CDATA   #REQUIRED ′ relation CDATA   #REQUIRED ′li_notes CDATA   #REQUIRED ′ li_desc CDATA   #REQUIRED ′ li_prec CDATA  #REQUIRED ′ li_unit CDATA   #REQUIRED ′ li_mag CDATA   #REQUIRED ′li_mod CDATA   #REQUIRED ′ li_measure CDATA   #REQUIRED ′ li_scale CDATA  #REQUIRED ′ li_adjustment    CDATA    #REQUIRED >′---------------------------------------------------------------------------------------Public Function fillLineItems(data As Range, litype As String)′Declarations Dim J, K As Integer Dim Max As Integer ′If this is anXYPlot, use the other routine If litype = “XYPlot” Then ′Fill_line_item_xy Else ′Initializations K = 1 buff = “” NumLI =data.Rows.Count ′Cycle through all the line items For N = 2 To NumLI′Insert opening tag buff = buff & “ <line_item” & Chr(10) ′Insert theAttributes addAttribute buff, “li_ID”, data.Cells(N, 1), 6, 0addAttribute buff, “li_legend”, data.Cells(N, 2), 6, 0 addAttributebuff, “li_title”, data.Cells(N, 3), 6, 0 addAttribute buff, “li_cat”,data.Cells(N, 4), 6, 0 addAttribute buff, “y_axis_title”, data.Cells(N,5), 6, 0 addAttribute buff, “level”, data.Cells(N, 6), 6, 0 addAttributebuff, “format”, data.Cells(N, 7), 6, 0 addAttribute buff, “relation”,data.Cells(N, 8), 6, 0 addAttribute buff, “li_notes”, data.Cells(N, 9),6, 0 addAttribute buff, “li_desc”, data.Cells(N, 10), 6, 0 addAttributebuff, “li_prec”, data.Cells(N, 11), 6, 0 addAttribute buff, “li_unit”,data.Cells(N, 12), 6, 0 addAttribute buff, “li_mag”, data.Cells(N, 13),6, 0 addAttribute buff, “li_mod”, data.Cells(N, 14), 6, 0 addAttributebuff, “li_measure”, data.Cells(N, 15), 6, 0 addAttribute buff,“li_scale”, data.Cells(N, 16), 6, 0 addAttribute buff, “li_adjustment”,data.Cells(N, 17), 6, 1 ′Fill the body of the tag with a comma-delimitedstring of the y-data numbers buff = buff & “  <data_y>” & Chr(10) MaxLI= NumLI − 2 MaxDP = data.Columns.Count − 17 For K = 1 To MaxDP  buff =buff & data.Cells(N, 18 + K) & “, ”  If (K Mod 10) = 0 Then   buff =buff & Chr(10)  End If Next K buff = buff & Chr(10) & “  </data_y>” &Chr(10) ′Insert ELEMENT: analysis ′Insert ELEMENT: li_class_set ′InsertELEMENT: ′linkset’ ′Call FillTag(“linkset”) ′Insert ELEMENT: note_set′Insert closing tag for that line item buff = buff & Chr(10) & “ </line_itern>” & Chr(10) ′Every 10 line items, flush the buffer ′If NMod 5 = 0 Then ′  Call SaveToFile(buff) ′End If Next N ′Closes the testfor XYPlot at beginning of routine End If fillLineItems = buff EndFunction′---------------------------------------------------------------------------------------Procedure:  addAttribute(name, value) ′ Purpose:  Adds an attribute lineto “buff” ′′---------------------------------------------------------------------------------------Public Sub addAttribute(buff, name, value, indent, last)  ′ Build theindentation  Dim strIndent As String  strIndent = “”  For J = 1 Toindent   strIndent = strIndent & “”  Next J  ′ Build the string  buff =buff & strIndent & name & “ = ” & Chr(34) & value & Chr(34)  ′Add anending ′>’ tag if “last” is 1; else simple add a carriage return  Iflast = 1 Then     buff = buff & “ >” & Chr(10)    Else     buff = buff &Chr(10)    End If   End Sub   Private Sub replaceAttribute(f As String,el As String, att As String, val As String)    f = Replace(f, att & “ =” & Chr(34) & Chr(34), att & “ = ” & Chr(34) & val & Chr(34))   End Sub  Private Sub fillXData(f As String)    ′build the string of X values   ′Dim data As Range    Dim v As String    t = RefEdit_data.value    v= Chr(10) & Range(t).Cells(1, 19)    For J = 20 ToRange(t).Columns.Count     v = v & “,” & Range(t).Cells(1, J)    Next J   v = v & Chr(10)    ′replace the current x data element text    f =Replace(f, “><../data_x>”, “>” & v & “ </data_x>”)   End Sub

1. An apparatus, comprising: a device; an application including anetwork browser installed on the device for accessing a systemconfigured for: identification of at least one computer-readableExtensible Markup Language (XML)-compliant data document capable ofincluding: a plurality of line items with a plurality of data values,and a plurality of computer-readable semantic tags that describe asemantic meaning of the data values, where the at least oneXML-compliant data document is capable of including multiplehierarchical relationships between two line items; parsing of the atleast one XML-compliant data document; accessing a plurality ofcomputer-readable rules including: a computer-readable datatype rule forvalidation of a type of data values, a computer-readable calculationrule for validation of a calculation involving data values, and acomputer-readable unit rule for validation of a unit of data values;validation of the at least one XML-compliant data document by:identifying at least a subset of the computer-readable rules includingat least one of: the computer-readable datatype rule for validation ofthe type of data values, the computer-readable calculation rule forvalidation of the calculation involving data values, or thecomputer-readable unit rule for validation of the unit of data values;processing at least a portion of the data values of at least a portionof the line items of the at least one XML-compliant data document,utilizing the at least subset of the rules and at least a portion of thecomputer-readable sematic tags of the at least one XML-compliant datadocument; and said apparatus configured for: accessing at least aportion of the at least one XML-compliant data document utilizing theapplication including the network browser.
 2. The apparatus of claim 1,wherein the system is configured to allow a user to select one or moreof the computer-readable semantic tags from a predetermined set ofcomputer-readable semantic tags and select one or more of the datavalues for mapping the one or more of the computer-readable semantictags to the one or more of the data values.
 3. The apparatus of claim 1,wherein the system is configured such that the computer-readablesemantic tags are each computer-readably coupled to at least one of thedata values.
 4. The apparatus of claim 1, wherein the system isconfigured such that the computer-readable semantic tags are searchable.5. The apparatus of claim 1, wherein the system is configured such thatthe computer-readable semantic tags each describe the semantic meaningof the data values via a computer-readable association between each ofthe computer-readable semantic tags and a corresponding line item of thedata values.
 6. The apparatus of claim 1, wherein the system isconfigured such that at least one of the computer-readable semantic tagsincludes a level tag for use in displaying the line items in a treeview.
 7. The apparatus of claim 1, wherein the system is configured suchthat the multiple hierarchical relationships between two line items aresearchable.
 8. The apparatus of claim 1, wherein the system isconfigured to cause referencing of a portion of an original document inconnection with at least one of the data values, such that, based on thereferencing, a change to the portion of the original document results ina corresponding change to the at least one data value.
 9. The apparatusof claim 1, wherein the system is configured such that the at least oneXML-compliant data document includes an extensible semantic tag-equippedmarkup language component and a hypertext markup language (HTML)component, and the at least one XML-compliant data document is capableof being displayed utilizing the network browser for allowing review ofthe HTML component in addition to access, through one or more additionalactions, the extensible semantic tag-equipped markup language component.10. The apparatus of claim 1, wherein the apparatus is configured suchthat at least one of: said identification of the at least oneXML-compliant data document includes receiving the at least oneXML-compliant data document; said at least one computer-readableXML-compliant data document includes a reusable data markup language(RDML) document; said line items are associated with a record, row,table, or other entity of a relational database; said computer-readablesemantic tags are applied to the line items; said computer-readablesemantic tags result from tagging; said computer-readable semantic tagsreflect characteristics including at least one of a magnitude, scale,modifier, unit, and measurement; said computer-readable semantic tagsreflect structure; said parsing includes at least one of: eliminatingwhite space, dividing input into words or groups of words, searching foropening or closing characters, relaying an error notice, or coordinatingupdating of component states; said computer-readable rules are stored ina document type definition (DTD); said computer-readable datatype rulefor validation of the type of data values includes a computer-readabledatatype rule for validation of a data value format; saidcomputer-readable calculation rule for validation of the calculationinvolving data values includes a computer-readable calculation rule forvalidation of a summation involving data values; said computer-readableunit rule for validation of the unit of data values includes acomputer-readable unit rule for validation of a currency of data values;said processing includes error checking; or said result includes anindication as to whether a defect is critical or not.
 11. A computerprogram product embodied on a non-transitory computer readable medium,comprising: code for storing a plurality of original documents includinga plurality of original values, including a first document includingfirst values and a second document including second values; code forprocessing at least a part of the first document and at least a part ofthe second document, resulting in at least one object including at leastone reference to at least one of the plurality of original values of atleast one of the plurality of original documents; code for receiving auser selection of one or more computer-readable semantic tags; code forreceiving a user selection of one or more of the original values; codefor mapping the one or more of the computer-readable semantic tags tothe one or more of the original values; code for outputting apresentation that is based on at least a portion of the at least oneobject, the presentation capable of including at least a portion of theoriginal values including the at least one original value, where thesystem is configured such that, based on the at least one reference ofthe at least one object to the at least one original value of the atleast one original document, a change to the at least one original valueof the at least one original document results in a corresponding changein a subsequent instance of the presentation; code for outputting areport that is based on at least a portion of the at least one object,the report capable of including at least a portion of the originalvalues including the at least one original value, where the system isconfigured such that, based on the at least one reference of the atleast one object to the at least one original value of the at least oneoriginal document, a change to the at least one original value of the atleast one original document results in a corresponding change in asubsequent instance of the report; and code for outputting at least onecomputer-readable Extensible Markup Language (XML)-compliant datadocument that is based on at least a portion of the at least one objectand at least a portion of the mapping, the at least onecomputer-readable XML-compliant data document capable of including aplurality of line items with at least a portion of the original valuesincluding the at least one original value and at least some of thecomputer-readable semantic tags, where the system is configured suchthat, based on the at least one reference of the at least one object tothe at least one original value of the at least one original document, achange to the at least one original value of the at least one originaldocument results in a corresponding change in a subsequent instance ofthe at least one computer-readable XML-compliant data document.
 12. Thecomputer program product of claim 11, wherein the computer programproduct is configured for utilizing a plurality of computer-readablerules for processing the at least one XML-compliant data document, thecomputer-readable rules including at least one of: a computer-readabledatatype rule for validation of a type of original values, acomputer-readable calculation rule for validation of a calculationinvolving original values, or a computer-readable unit rule forvalidation of a unit of original values.
 13. The computer programproduct of claim 11, wherein the computer program product is configuredfor utilizing a plurality of computer-readable rules for validating theat least one XML-compliant data document, the computer-readable rulesincluding: a computer-readable datatype rule for validation of a type oforiginal values, a computer-readable calculation rule for validation ofa calculation involving original values, and a computer-readable unitrule for validation of a unit of original values.
 14. The computerprogram product of claim 11, wherein the computer program product isconfigured for validating the at least one XML-compliant data documentby: identifying at least a subset of the computer-readable rulesincluding at least one of: a computer-readable datatype rule forvalidation of a type of original values, a computer-readable calculationrule for validation of a calculation involving original values, or acomputer-readable unit rule for validation of a unit of original values;and processing at least the portion of the original values of the atleast one XML-compliant data document, utilizing the at least subset ofthe rules and at least a portion of the computer-readable sematic tagsof the at least one XML-compliant data document.
 15. The computerprogram product of claim 11, wherein the computer program product isconfigured such that the at least some of the computer-readable semantictags are each computer-readably coupled to the at least portion of theoriginal values.
 16. The computer program product of claim 11, whereinthe computer program product is configured such that the at least someof the computer-readable semantic tags describe a semantic meaning ofthe at least portion of the original values via a computer-readableassociation between each of the at least some of the computer-readablesemantic tags and a corresponding line item.
 17. The computer programproduct of claim 11, wherein the computer program product is configuredsuch that at least one of the computer-readable semantic tags includes alevel tag for use in displaying the line items in a tree view.
 18. Thecomputer program product of claim 11, wherein the computer programproduct is configured such that the at least one XML-compliant datadocument is capable of including multiple hierarchical relationshipsbetween two line items.
 19. The computer program product of claim 11,wherein the computer program product is configured such that at leastone of: said at least portion of the original values of the at least onecomputer-readable XML-compliant data document include differentinstances of the same values as the corresponding original values of theat least one original document; said mapping includes an association;said at least some of the computer-readable semantic tags includes allof the one or more of the computer-readable semantic tags subject to themapping; said at least one object includes at least one of metadata,information, a component of a formatter, a storage object, or adatabase; said at least one computer-readable XML-compliant datadocument includes a reusable data markup language (RDML) document; saidline items are associated with a record, row, table, or other entity ofa relational database; said presentation, the report, and the at leastone computer-readable XML-compliant data document include the same atleast portion of the original values; said presentation, the report, andthe at least one computer-readable XML-compliant data document includethe same at least one original value; said presentation, the report, andthe at least one computer-readable XML-compliant data document are basedon the same at least portion of the at least one object; said at leastone computer-readable XML-compliant data document is based on the atleast portion of the at least one object by including the at leastportion of the at least one object; said at least one computer-readableXML-compliant data document is based on the at least portion of the atleast one object by being generated utilizing the at least portion ofthe at least one object; said at least one computer-readableXML-compliant data document is based on the at least portion of themapping by including the at least some of the computer-readable semantictags; said at least some of the computer-readable semantic tags areincluded in the line items; said change to the at least one originalvalue of the at least one original document is capable of being made inthe at least one original document; said corresponding change in thesubsequent instance of the at least one computer-readable XML-compliantdata document includes a change to an instance of the at least oneoriginal value in the at least one computer-readable XML-compliant datadocument; said subsequent instance of the at least one computer-readableXML-compliant data document is subsequent to the change to the at leastone original value of the at least one original document; or saidcomputer-readable semantic tags are applied to the line items.
 20. Amethod, comprising: storing a plurality of original documents includinga plurality of original values, including a first document includingfirst values and a second document including second values; processingat least a part of the first document and at least a part of the seconddocument, resulting in at least one object including at least onereference to at least one of the plurality of original values of atleast one of the plurality of original documents; receiving a userselection of one or more computer-readable semantic tags; receiving auser selection of one or more of the original values; mapping the one ormore of the computer-readable semantic tags to the one or more of theoriginal values; outputting a presentation that is based on at least aportion of the at least one object, the presentation capable ofincluding at least a portion of the original values including the atleast one original value, where the system is configured such that,based on the at least one reference of the at least one object to the atleast one original value of the at least one original document, a changeto the at least one original value of the at least one original documentresults in a corresponding change in a subsequent instance of thepresentation; outputting a report that is based on at least a portion ofthe at least one object, the report capable of including at least aportion of the original values including the at least one originalvalue, where the system is configured such that, based on the at leastone reference of the at least one object to the at least one originalvalue of the at least one original document, a change to the at leastone original value of the at least one original document results in acorresponding change in a subsequent instance of the report; andoutputting at least one computer-readable Extensible Markup Language(XML)-compliant data document that is based on at least a portion of theat least one object and at least a portion of the mapping, the at leastone computer-readable XML-compliant data document capable of including aplurality of line items with at least a portion of the original valuesincluding the at least one original value and at least some of thecomputer-readable semantic tags, where the system is configured suchthat, based on the at least one reference of the at least one object tothe at least one original value of the at least one original document, achange to the at least one original value of the at least one originaldocument results in a corresponding change in a subsequent instance ofthe at least one computer-readable XML-compliant data document.